kdb Insights Enterprise - Release Notes

Database

• You can now load a UDA without restarting core components like Data Access Processes (DAPs) and Aggregators (AGGs). This feature provides users with a faster, improved workflow for testing and deploying changes. Refer to Load a Package.

• The performance of loading table counts have been improved through more efficient caching.

• You can now configure the Service Gateway to connect to multiple Resource Coordinators, enhancing query resilience. To enable this, set the KXI_SG_RC_ADDR environment variable on the Service Gateway to a comma-separated list of Resource Coordinator addresses. For example, KXI_SG_RC_ADDR=sgrc:5050,sgrcalt:5050 . See Query Resilience.

• Distinguished parameter scope now takes dap as a key to allow a user to target a specific DAP in a query. Note this parameter is supported only if scope.assembly is specified, and it cannot be used with scope.tier. Refer to Scope for more details.

• The getMeta API has been improved to give users better visibility of their system's processes. The dap key of getMeta now gives detail on individual DAPs when the new parameter advanced is set to true. Previously, getMeta would expose information only on tiers, but not individual processes. Refer to Get-meta .

Packaging

When deleting a package, the user can now choose whether to delete all data related to the package. This includes database contents, pipeline checkpoints, and user states.

Database

• Resolved an issue that prevented using peaching over arguments with .kxi.selectTable. For example: .kxi.selectTable peach 4#enlist`table`startTS`endTS`filter!(table;startTS;endTS;enlist(in;`sym;enl`nada))

• .kxi.sql queries that use EXCEPT ALL have been corrected to align with postgreSQL behavior, in which duplicates would be included in query results.

Packaging

• Resolved an issue where the Package Manager was unable to unpack a package that contained a user-defined function.

• Packages now allow column names to end with _ .

Web Interface

• The Performance Tuning Wizard previously allowed users to attempt re-sorting data already on-disk - an unsupported operation that caused failures. To prevent this, the Performance Tuning Wizard will no longer be available once data has been ingested into the database.

Security

• Various CVEs were remediated as part of this release.