-
Bug
-
Resolution: Done
-
Major
-
None
-
None
What Debezium connector do you use and what version?
Debezium server version 3.0
What is the connector configuration?
application.properties snippet:
```
debezium.transforms=outbox
debezium.transforms.outbox.type=io.debezium.transforms.outbox.EventRouter
debezium.transforms.outbox.route.by.field=aggregate_type
debezium.transforms.outbox.table.field.event.id=id
debezium.transforms.outbox.table.field.event.key=aggregate_id
debezium.transforms.outbox.table.field.event.payload=payload
debezium.transforms.outbox.table.fields.additional.placement=event_type:header:event_type
debezium.transforms.outbox.tracing.span.context.field=trace_span_context
debezium.transforms.outbox.tracing.operation.name=debezium-read
```
What is the captured database version and mode of deployment?
Local development with postgres source
What behavior do you expect?
The published event in jetstream should have "id, event_type, trace_span_context" in headers
What behavior do you see?
Headers are empty