oscerd opened a new pull request, #23244:
URL: https://github.com/apache/camel/pull/23244

   ## 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.x`
   **Fix versions:** 4.14.8, 4.18.3, 4.21.0
   
   ### What this changes
   
   Renames the Exchange header string values in 
`ElasticSearchRestClientConstant`
   to 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.
   
   | 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` |
   
   ### Cherry-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 on `main`
   across all releases), so it was dropped from this backport. A separate
   doc-sync PR against `main` adds the matching
   `camel-4x-upgrade-guide-4_18.adoc` entry for this rename.
   
   ### Test plan
   
   - [x] Full reactor `mvn clean install -DskipTests` succeeds on 
`camel-4.18.x` after the cherry-pick.
   
   ---
   
   _Claude Code on behalf of Andrea Cosentino_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to