@Alvin Shih

Morgan Stanley

alvin-c-shih

@Aitana Myohl

FINOS

aitana16

@James McLeod (Unlicensed)

FINOS

mcleo-d

Aaron Davies

Morgan Stanley

adavies42

Alok Dutt

Citi

Gary Davies

AquaQ

@Kai Zeng

UBS

Peter Gyorok

Morgan Stanley

gyorokpeter

Tim Beletskiy

JP Morgan

5 min

Convene & roll call.

All

5 min

Review and approve minutes from last meeting.

All

• Approved by acclamation.

20 min

memusage.q and timer merged to master.

Any news about microsite for documentation?

All

• James provided some clarification on microsites.
  
  

  • Docusaurus + React

    • React provides the structure.

    • Authored as *.md files.

  • Example site: https://fo.finos.org/

    • Source code: https://github.com/finos/finos-fo/tree/master/website

    • FINOS has CI / CD hooks that look for pull requests and rebuild the site.

  • Email help@finos.org to get started.

20 min

Best practices for extending HDB functionality?

Some ideas from last time:

• Sparse HDB / Partial HDB reload

  • Push old functions to be callable from somewhere?

  • Only hook entry points and reimplement everything under .finos?

  • Detect changes in implementation of upstream functions using a hash?

• Staging Directory / Archive Directories

  • How to specify?

  • finos_hdb_config/ under HDB root?

  • *.q file to verify correct extensions are loaded?

All

• Some discussion of the HDB well-formedness doc first.
  
  

  • Aaron said that the information contained therein exists in various places.

  • The main benefit is seeing it all in one place.

    • Could use more detail on AnyMap.

  • Could start writing unit tests for HDB functionality based on the doc.

    • Aaron might have a few tests lying around.

  • Good to have before embarking on any HDB extensions.

• Extending HDB functionality?

  • Significant interest in the ability to load multiple HDBs.

    • Some have heard that Kx is looking into it.

    • Questions as to any restrictions on joins between HDBs.

  • Many of the interesting extensions are not backwards compatible.

    • Need a *.q file in the HDB root to verify that correct extensions are loaded.

    • MD5 hashes of .Q.ps to detect stock vs. custom HDB logic.

  • .Q.l extensions

    • Adds staging directories as extra argument?

    • Or maybe looks for an alternative to par.txt since there might have to be one staging directory per segment for performance.

• How might FINOS and Kx collaborate?

  • Boost C++ libraries are something of a testing ground.

  • Those which get wide usage are then used as the basis for additions to the C++ Standard Library.

    • Sometimes the API receives significant changes before being incorporated into the standard.

  • Analogously, Kx could see what might be worth incorporating directly in to kdb.

    • Those features that they don't want to support directly, they could add hooks to facilitate extension.

    • For example, .z.ph implementation was changed to call .h.val to allow authorization handlers to validate requests in HTML mode.

• Hiding files related to HDB extensions?

  • Hide files using trailing '$'?

    • Seems like a nonzero risk of being overwritten.

  • html/ directory can contain anything.

    • Risk of unintentionally serving configuration information / code over HTTP?

  • Maybe a single directory ending in '$', like "finos$/"?

  • Ignore .Q.l completely?

    • .finos.hdb.load[...]

• Backwards compatible enhancements?

  • .Q.chk with peach support.

  • Support alternate partitionings.

    • Currently limited to: date, month, year, or int.

    • Desirable partition types include: long, timestamp.

10 min

Demo of Docusaurus.

• James gave a quick demo on his MacBook.
  
  

  • cd website/

  • npm install

  • npm start

    • Starts the microsite locally for preview.

• Much more understandable after seeing it in action.

5 min

AOB

All