This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch doc-sync/CAMEL-23508-4.14-guide in repository https://gitbox.apache.org/repos/asf/camel.git
commit bfa0cd4767b6d7cc04378fe98775d94d28237fab Author: Andrea Cosentino <[email protected]> AuthorDate: Wed May 20 11:08:40 2026 +0200 CAMEL-23508: document 4.14.8 camel-elasticsearch-rest-client header rename in upgrade guide Signed-off-by: Andrea Cosentino <[email protected]> --- .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 23 ++++++++++++++++++++++ 1 file changed, 23 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 7bc6f56b514a..4ed15b2bda5c 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 @@ -156,6 +156,29 @@ this pattern now fails fast with an `IllegalArgumentException` (wrapped in a `Neo4jOperationException`) instead of producing a malformed query. Property values continue to be passed as bound query parameters and are unaffected. +=== camel-elasticsearch-rest-client + +The Exchange header constants in `ElasticSearchRestClientConstant` have been +renamed to follow the Camel naming convention used across the rest of the +component catalog. The Java field names are unchanged; only the header string +values have changed: + +[options="header"] +|=== +| Constant | Previous value | New value +| `ElasticSearchRestClientConstant.ID` | `ID` | `CamelElasticsearchId` +| `ElasticSearchRestClientConstant.SEARCH_QUERY` | `SEARCH_QUERY` | `CamelElasticsearchSearchQuery` +| `ElasticSearchRestClientConstant.INDEX_SETTINGS` | `INDEX_SETTINGS` | `CamelElasticsearchIndexSettings` +| `ElasticSearchRestClientConstant.INDEX_NAME` | `INDEX_NAME` | `CamelElasticsearchIndexName` +| `ElasticSearchRestClientConstant.OPERATION` | `OPERATION` | `CamelElasticsearchOperation` +|=== + +Routes that reference the constant symbolically (for example +`setHeader(ElasticSearchRestClientConstant.SEARCH_QUERY, ...)`) continue to +work without changes. Routes that set the header by its literal string value +(for example `setHeader("SEARCH_QUERY", ...)`) must be updated to use the +new value (`setHeader("CamelElasticsearchSearchQuery", ...)`). + == Upgrading from 4.14.2 to 4.14.3 === camel-tika
