Skip to content

Release Notes - Microservices 1.1.2

kdb Insights Microservices 1.1.2 release.

Release Date



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 getData() API

[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 getData 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.

Known Issues

  • 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
   {"header":{"http":"json","corr":"6dd8f0c5-1895-49c9-a87a-636a834af370","logCorr":"6dd8f0c5-1895-49c9-a87a-636a834af370","client":":","api":".kxi.getData","protocol":"gw","numRP":1,"ogRcID":"","to":"2022-04-07T11:41:35.717000000","retryCount":0,"rc":42,"ac":10,"ai":"Agg died"},"payload":[]}

Upgrade considerations


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 insig..

Database (Service Gateway, Data Access, Storage Manager)

  • Critical invalid configuration will now fatally exit the process with a FATAL log message and information on the configuration error
  • Assembly mounts.*.uri is now defined as mounts.*.baseURI - existing assembly files will need to be updated accordingly
  • Update to RT Client Library for new API signatures:


Service Discovery

microservice Docker Helm Chart
Discovery Registry
Discovery Proxy

Stream Processor

microservice Docker qpk

Data Access

microservice Docker
Data Access Process (DA)

Storage Manager

microservice Docker
Storage Manager
End of Interval (EOI)
End of Day (EOD)
Database Migration (DBM)
Single Container

Service Gateway

microservice Docker
Resource Coordinator

User interface

microservice Docker Helm Chart

Machine Learning

microservice package
ML Registry
ML Analytics


microservice Docker package
Metrics Sidecar
OpenAPI SDK Generator