[backport camel-4.18.x] CAMEL-23508: camel-elasticsearch-rest-client - align Exchange header constant names with Camel naming convention#23244
Merged
oscerd merged 1 commit intoMay 15, 2026
Conversation
…constant names with Camel naming convention Rename the Exchange header string values in ElasticSearchRestClientConstant from raw uppercase (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) to the Camel naming convention (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation). The Java field names are unchanged so routes referencing the constants symbolically continue to work. Routes using the literal string value must be updated. Adds an entry to the 4.21 upgrade guide and regenerates the affected component metadata, catalog, and endpoint DSL. Closes apache#23212
Merged
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #23212
Cherry-pick of #23212 onto
camel-4.18.x.Original PR: #23212 — CAMEL-23508: camel-elasticsearch-rest-client - align Exchange header constant names with Camel naming convention
Original author: @oscerd
Target branch:
camel-4.18.xFix versions: 4.14.8, 4.18.3, 4.21.0
What this changes
Renames the Exchange header string values in
ElasticSearchRestClientConstantto the Camel naming convention. The Java field names are unchanged, so
routes referencing the constants symbolically continue to work without
changes. Routes that use the literal string value must be updated.
ElasticSearchRestClientConstant.IDIDCamelElasticsearchIdElasticSearchRestClientConstant.SEARCH_QUERYSEARCH_QUERYCamelElasticsearchSearchQueryElasticSearchRestClientConstant.INDEX_SETTINGSINDEX_SETTINGSCamelElasticsearchIndexSettingsElasticSearchRestClientConstant.INDEX_NAMEINDEX_NAMECamelElasticsearchIndexNameElasticSearchRestClientConstant.OPERATIONOPERATIONCamelElasticsearchOperationCherry-pick notes
The original commit also modified
camel-4x-upgrade-guide-4_21.adoc.That file does not exist on
camel-4.18.x(it is canonical onmainacross all releases), so it was dropped from this backport. A separate
doc-sync PR against
mainadds the matchingcamel-4x-upgrade-guide-4_18.adocentry for this rename.Test plan
mvn clean install -DskipTestssucceeds oncamel-4.18.xafter the cherry-pick.Claude Code on behalf of Andrea Cosentino