Repository navigation
Release v1.0.2
Description
A patch release: a kafka source can read several topics at once, a lookup through a plugin or through transform/filter middlewares stays batched, and the CLI gets an agent skill. Nothing needs a change when upgrading from 1.0.1; a plugin that uses the new x-mqb-uri: filepath needs this release.
- New features
- A
kafkasource reads several topics.topictakes a list ([orders.eu, orders.us]) or a comma-separated string, and one consumer group shares the partitions of all of them;--drainends once every listed topic is read to its end. On the CLI the list is?topic=a,b. A name starting with^is a librdkafka regex; a drain now refuses a pattern, because it could not see the partitions its peers held and could end early. Akafkaoutput with a list or a pattern fails at startup instead of writing to a topic named after it. - An agent skill for the CLI. It teaches Claude Code, Codex and other agents that read
SKILL.mdto usemqb list,describe,copyand config files. Install it withnpx skills add marcomq/mq-bridge. x-mqb-uri: filepathfor plugin schemas. Likepath, but the leading/stays, sox:///models/a.onnxgives/models/a.onnx.
- A
- Performance
- A
lookupthrough a plugin is one call per batch. A plugin with ABI 1.2 or newer answers the whole batch in onesend_batch, and each request fails on its own. An older plugin, or a batch with repeated message ids, is still asked one request at a time. transform,filterand plugin middlewares on a lookup'sfromkeep it batched instead of turning it into one request per message.
- A
- Fixed
- The JSON schema accepts the descriptive format names (
envelope,payload,envelope_json,envelope_text), so an editor that validates againstmq-bridge.schema.jsonno longer marks them invalid, andmqb describelists them.
- The JSON schema accepts the descriptive format names (
The full list is in the changelog.
Full Changelog: v1.0.1...v1.0.2