Release Notes - Microservices 1.1.2
kdb Insights Microservices 1.1.2 release.
Storage Manager & Data Access
[NEW] Late and out-of-order data handling
[NEW] Data received out of order is recorded with an appropriate ingest timestamp
[NEW] Late data is recorded, irrespective of where its correct destination is in the lifecycle (RDB, IDB, HDB)
[NEW] Late data is included by default for all requests,
getData and ANSI SQL
[NEW] Late data can be filtered out (for example, to see only data present in the system at a particular point in time)
[NEW] Performance is not significantly impacted by late data arrival
[NEW] Reference data can be queried in the Explore Window, in a data pipeline and as part of the
[NEW] Support for non time-series reference data in Database
[NEW] Data in reference tables can be joined to time-series tables in free-form q queries or
Improved SQL support for queries (joins and complex queries, except for reference tables)
[NEW] Compression support, including object storage
[NEW] Improved resiliency and performance
[FIX] The getData API endpoint no longer returns an error when an
outputTZ is provided.
[FIX] Queries against the interval tier (idb) around the end-of-day rollover process could return zero results.
[FIX] Reference data joins which do not include the foreign column or where the foreign column has a different name are now possible.
[FIX] An issue where certain queries using
count could throw the error
Error: noupdate: `.Q `pn has been resolved.
- If you request too much data in a single getData(), the request will fail. To overcome this issue you should request less data per getData() call. The error message returned will look like the example below
From 1.1.0 licensing changes are included to enable feature and comsumption based licensing in some cases. As part of this Microservices now require clients to upgrade to new licenses with feature flags. Previous licenses only required
KXCE in the banner.
To validate if a license has feature flags, start a process or Microservice using it and check
.z.l 4 in the terminal. This should return something like
"insights.lib.embedq insights.lib.pykx insights.lib.sql insights.app.rt insig..
Database (Service Gateway, Data Access, Storage Manager)
- Critical invalid configuration will now fatally exit the process with a
FATALlog message and information on the configuration error
mounts.*.uriis now defined as
mounts.*.baseURI- existing assembly files will need to be updated accordingly
- Update to RT Client Library for new API signatures: https://code.kx.com/insights/1.1/microservices/storage-manager/sm-interface.html#interface-with-a-messaging-service
|Data Access Process (DA)||registry.dl.kx.com/kxi-da:1.1.2|
|End of Interval (EOI)||registry.dl.kx.com/kxi-sm-eoi:1.1.0|
|End of Day (EOD)||registry.dl.kx.com/kxi-sm-eod:1.1.0|
|Database Migration (DBM)||registry.dl.kx.com/kxi-sm-dbm:1.1.0|
|OpenAPI SDK Generator||registry.dl.kx.com/kxi-openapi-codegen:0.8.0||https://nexus.dl.kx.com/repository/kx-insights-packages/kxi-openapi-codegen/0.8.0/kxi-openapi-codegen-0.8.0-shaded.jar|