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 22a0c0db93df CAMEL-23597: docs - sync camel-solr 4.14 upgrade-guide
entry to main (#23493)
22a0c0db93df is described below
commit 22a0c0db93dfdcb1ea76450a4e1625bf559bcfdc
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue May 26 11:24:56 2026 +0200
CAMEL-23597: docs - sync camel-solr 4.14 upgrade-guide entry to main
(#23493)
Doc-sync companion to the 4.14.x backport (#23489). Adds the camel-solr
Exchange header prefix rename note from camel-4.14.x to the canonical
camel-4x-upgrade-guide-4_14.adoc on main, so main's 4_14 guide stays in
sync with the matching maintenance-branch guide. Identical text; no code
change.
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 31 ++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 61e538bb690a..7fc2956a8d7f 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -287,6 +287,37 @@ have been renamed accordingly:
* `gridfsObjectid()` -> `gridFsObjectId()`
* `gridfsFileid()` -> `gridFsFileId()`
+=== camel-solr
+
+The two Exchange header prefix constants in `SolrConstants` have been renamed
to
+follow the Camel naming convention already used by the other constants in the
+same file (which were renamed in 4.10 under CAMEL-21697). The Java field names
+are unchanged; only the prefix string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `SolrConstants.HEADER_FIELD_PREFIX` | `SolrField.` | `CamelSolrField.`
+| `SolrConstants.HEADER_PARAM_PREFIX` | `SolrParam.` | `CamelSolrParam.`
+|===
+
+Routes that reference the constants symbolically (for example
+`setHeader(SolrConstants.HEADER_FIELD_PREFIX + "id", ...)`) continue to work
+without changes. Routes that set the headers by their literal string value
+(for example `setHeader("SolrField.id", ...)` or
+`setHeader("SolrParam.commit", ...)`) must be updated to use the new prefix
+(`CamelSolrField.id`, `CamelSolrParam.commit`).
+
+Because the renamed prefixes now begin with `Camel`, they are stripped by the
+standard transport `HeaderFilterStrategy` (`HttpHeaderFilterStrategy`, etc.)
+when crossing a transport boundary, by design — `Camel*` headers are
+framework-internal and are not propagated over the wire. Routes that bridge an
+external transport (HTTP, JMS, ...) into a `solr:` producer and want to drive
+Solr document fields or query parameters from a header supplied by the sender
+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`.
+
== Upgrading from 4.14.2 to 4.14.3
=== camel-tika
