MeridianKafkaAdapter

meridian-storage-kafka is the Apache Kafka engine adapter for the released Meridian streaming Catalog. This public repository owns exactly this one Python distribution and contributes only meridian_storage.adapters.kafka.

Applications never import this package or confluent_kafka. They use the mapping-first streaming Catalog methods from meridian-storage-streaming: publish, publish_batch, subscribe, poll, acknowledge, negative_acknowledge, and read_range. Replay and ConsumerGroup position changes remain explicit versioned Operations. Deployment IaC installs and selects this adapter through a closed Meridian Binding.

Compatibility

Version 1.0.0 is pinned to:

Kafka 3.9.2 and 4.0.2 are documented only as archived migration-source boundaries and are not accepted by the runtime or part of the supported production matrix. See docs/compatibility.md for the exact capability and evidence policy.

Install

The adapter is installed only at a composition or deployment boundary:

python -m pip install \
  meridian-storage-core==1.0.0 \
  meridian-storage-semantics==1.0.0 \
  meridian-storage-streaming==1.0.0 \
  meridian-storage-kafka==1.0.0

Core discovers the immutable meridian.kafka factory through the meridian_storage.adapters entry-point group. A Binding supplies opaque identity, credential, TLS, topic, group, schema, Capability, and physical fingerprints. Startup performs authenticated probes and read-only physical verification; it never creates topics, changes partitions or retention, installs ACLs, or owns broker/controller lifecycle.

Guarantees

• At-least-once delivery by default, with ordering only within one logical partition.
• Opaque, authenticated Cursors, positions, and delivery tokens; raw Kafka topics, partitions, offsets, groups, and generations are never public Data.
• Monotonic safe-position acknowledgement, negative acknowledgement and redelivery, explicit dead-letter routing, and retained finite range reads.
• Idempotent Kafka production. Transactional consume-publish is advertised only when its single-Binding and committed-read preconditions are enabled.
• Stable Meridian failures with Kafka details retained only as redacted adapter diagnostics.
• Generic audit, lineage, telemetry, lag, rebalance, transaction, and probe evidence through the configured composition boundary.

Authority boundary

Platform or Vangu IaC through MeridianConstructs owns engine selection, provisioning or external reference, state, identities, secrets, ACLs, topic and partition migrations, retention, compaction, recovery, and broker/controller lifecycle. This runtime validates those outputs. It has no infrastructure mutation API and no NativeQuery surface.

See docs/architecture.md, docs/operations.md, and docs/security-and-lifecycle.md.

Development and conformance

python -m pip install -e '.[test]'
ruff check .
ruff format --check .
mypy src scripts conformance/scripts tests
pytest -q -m 'not cluster'
python conformance/scripts/run_cluster.py --kafka-version 4.3.1 --full
python conformance/scripts/run_cluster.py --kafka-version 4.2.1
python conformance/scripts/run_cluster.py --kafka-version 4.1.2

The primary real-cluster profile runs the full acceptance matrix against Apache Kafka 4.3.1. Compatibility profiles repeat portable semantics against 4.1.2 and 4.2.1. Cluster evidence is emitted as a deterministic JSON report and attached to each release with its SPDX SBOM and provenance attestations.

License

Apache License 2.0. See LICENSE and NOTICE.