This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new d3072d9ff93e CAMEL-23630: Document camel-dapr consumer header change
in 4.18 upgrade guide (#23891)
d3072d9ff93e is described below
commit d3072d9ff93edbcc80c8fa42d1067636b4748ff8
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed Jun 10 09:02:12 2026 +0200
CAMEL-23630: Document camel-dapr consumer header change in 4.18 upgrade
guide (#23891)
The dapr-pubsub consumer header change (CAMEL-23630) was backported to
camel-4.18.x (#23889) and ships in 4.18.3. Per the backport upgrade-guide
policy, document it in camel-4x-upgrade-guide-4_18.adoc on main (the
canonical
upgrade-guide history), mirroring the existing 4_21 entry.
Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 33 ++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 797769972bc1..c5ceaf47b286 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -950,6 +950,39 @@ must therefore carry the value in a non-`Camel`-prefixed
application header and
map it to the appropriate `CamelSolrField.*` / `CamelSolrParam.*` header in the
route between the transport `from` and the `solr:` `to`.
+=== camel-dapr - potential breaking change
+
+The `dapr` component now ships a default `DaprHeaderFilterStrategy` (extending
+`DefaultHeaderFilterStrategy`) and exposes it via the standard
`headerFilterStrategy`
+endpoint/component option, aligning the component with the rest of the Camel
component
+catalog (`camel-iggy`, `camel-kafka`, `camel-jms`, ...). The strategy filters
headers
+starting with `Camel` / `camel` (case-insensitive) in both directions.
+
+In addition, the `dapr-pubsub` consumer no longer copies the inbound
CloudEvent's
+`pubsubName` and `topic` into the `CamelDaprPubSubName`
(`DaprConstants.PUBSUB_NAME`)
+and `CamelDaprTopic` (`DaprConstants.TOPIC`) message headers. These two
constants are
+producer-direction routing headers: they are read back on the producer side by
+`DaprConfigurationOptionsProxy` and take precedence over the
endpoint-configured
+`pubSubName` / `topic`. Setting them on a consumed exchange caused a route
such as
+
+[source,java]
+----
+from("dapr-pubsub:configured-pubsub:configured-topic")
+ .to("dapr-pubsub:configured-pubsub:another-topic");
+----
+
+to carry the inbound pubsubName / topic into the producer hop instead of using
the
+configured destination. The remaining CloudEvent metadata headers
(`CamelDaprID`,
+`CamelDaprSource`, `CamelDaprType`, `CamelDaprSpecificVersion`,
+`CamelDaprDataContentType`, `CamelDaprBinaryData`, `CamelDaprTime`,
+`CamelDaprTraceParent`, `CamelDaprTraceState`) are unchanged and are still set
on the
+inbound exchange.
+
+Because a `dapr-pubsub` consumer subscribes to a single, fixed `pubSubName` /
`topic`,
+the removed headers were redundant with the endpoint configuration. Routes
that relied
+on reading `CamelDaprPubSubName` / `CamelDaprTopic` from a consumed exchange
should read
+the configured destination from the endpoint URI instead.
+
== Upgrading from 4.18.0 to 4.18.1
=== camel-bom
