Primary Site v0.0.106
When resolving a recording's context, this release merges every "foxglove" MCAP metadata record in the file, rather than using only the last one. Later records override earlier keys, and an empty string value unsets a key. To keep the previous behavior, set the following in your values.yaml, on whichever component your indexing strategy deploys:
inboxListener:
deployment:
mergeFoxgloveMcapMetadata: false
This release also adds an optional beta stream executor, which can substantially improve streaming throughput on multi-core query service pods. It is off by default.
Added
- Added a beta multi-threaded stream executor that reads a stream's MCAP chunks across parallel partitions, off by default behind
queryService.deployment.enableBetaStreamExecutor
Changed
- Merged all
"foxglove"MCAP metadata records when resolving recording context, instead of using only the last record. SetmergeFoxgloveMcapMetadata: falseon the indexer or inbox listener deployment to restore the previous last-record-only behavior
Fixed
- Improved query service error messages when a stream fails mid-response
- Fixed
values.yamlvalidation, which was silently skipping its required-setting checks