2019-07-01 kdb+ WG Minutes

Meeting minute status: Approved (on 8/5/2019)


Table of Contents

Date/Time

  • July 1, 2019. 11am ET

Attendees

NameOrganisationGithub ID 
Rob Underwood (Deactivated)FINOSbrooklynrob
Aitana MyohlFINOS
Alvin ShihMorgan Stanleyalvin-c-shih
Aaron DaviesMorgan Stanleyadavies42
Peter GyorokMorgan Stanleygyorokpeter
Jason Foster-BeyJP Morgan
Latchezar NikolovMorgan Stanley
Yair MarcowMavenomics


Action Items

Tasks Identified and Assigned

  • Alok to reach out to BAML and GS
  • Alvin Shih to send out conventions that get used for qualifying names.

Task Report from the Last Meeting

(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)

DescriptionDue dateAssigneeTask appears on
  • Asking about license for developers
2018-09-05 kdb+ WG Minutes
  • Decision - How to make use of the Kx/Kdb naming space in a consistent way across firms
2018-09-05 kdb+ WG Minutes
  • Share sample tests, configurations, in part to start to create guidelines for naming (on-going task as working group stands up)
2018-09-05 kdb+ WG Minutes

Decisions Made


Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call.

All


5 minReview and approve minutes from last meeting.AllApproved by acclamation.
5 minDiscuss authz_ro pull request.  Useful enough to merge to master?  Anybody want to contribute some finishing touches?All

Question about Kx commenting convention raised again.

Does .z.pp need a default implementation?  No.  Does nothing by default.

Does .z.pq need a default implementation?  Yes.  Use the same handler as for .z.pg.

Suggestion about including best practices to add RW users to the documentation.

5 minDiscuss structlog pull request. Is this something you'd use yourself?  Standardized dictionary keys?  Any contributions in terms of pipeline stages?  (With a good set of standard keys, could have utilities that scrub sensitive info in Prod, etc.)All

Discussion to be taken to email.

5 minq style alignment with python?  Leading underscore to indicate "protected" and leading double underscore to indicate "private"?All

q doesn't like leading underscores in various contexts.

foo._a:1 works, but \d .foo followed by _a:1 does not.

`_a does not parse as a legal symbol.

Although some of us don't like using \d , there might be a nontrivial portion of the kdb community who do.

Scrapping the idea.

5 minStatus update on HDB well-formedness document.All

Has been updated based on feedback inside Morgan Stanley.

Scripts that generate appropriate test HDBs to allow readers to verify various claims for themselves and / or support unit tests are under development.

Possibly another month before a draft is made externally available.

5 minUpdate on "include" and "InitHook"?All

"include" library may be pushable soon.  Implementation should be MS-Windows compatible.

` vs doesn't split on "\" on Windows.  Morgan Stanley should submit a KXTRACK ticket for that.

5 minFDX: Any blockers to contribution we can help with?AllAttempt to push "include" code blocked at proxy.  Probably just propagation delay for new permissions.
5 minOther goings on in DT: Data Helix (data generator) and Exodus (schema migration tool).All

No comments from kdb+ WG at the moment.


5 minPublic cloud?  Service discovery?All

Kx has done presentations on how they work with Google Cloud, AWS.

https://www.firstderivatives.com/cloud-academy/

Not much use of cloud among current kdb+ WG members.

Should the time come, we could check in with FDX and the Cloud Service Certification Project.

5 minAOBAll

Action Items

  • Jason Foster-Bey to start follow-up thread re:structlog
  • Aaron Davies to send out HDB consistency doc.
  • Peter Gyorok to put "include" on GitHub.
  • Alvin Shih to put together qstructlog PoC.
  • Aaron Davies to get Symphony access to discuss authz_ro with Jason Foster-Bey.
  • Aaron Davies to get approvals for pushing kdb+ WG-related work to GitHub.

Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.