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

   ## Backport of #23212
   
   Cherry-pick of #23212 onto `camel-4.14.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.14.x`
   
   ### Changes
   
   Renames the Exchange header string values in 
`ElasticSearchRestClientConstant`
   from raw uppercase (`ID`, `SEARCH_QUERY`, `INDEX_SETTINGS`, `INDEX_NAME`,
   `OPERATION`) to the `CamelElasticsearch*` prefix used across the rest of the
   component catalog. Java field names are unchanged - only the header string
   values change.
   
   | Constant | Previous value | New value |
   | --- | --- | --- |
   | `ID` | `ID` | `CamelElasticsearchId` |
   | `SEARCH_QUERY` | `SEARCH_QUERY` | `CamelElasticsearchSearchQuery` |
   | `INDEX_SETTINGS` | `INDEX_SETTINGS` | `CamelElasticsearchIndexSettings` |
   | `INDEX_NAME` | `INDEX_NAME` | `CamelElasticsearchIndexName` |
   | `OPERATION` | `OPERATION` | `CamelElasticsearchOperation` |
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-23508
   
   ### Conflict resolution
   
   The cherry-pick had a single `modify/delete` conflict on
   `docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc`. That
   file does not exist on the `camel-4.14.x` branch, so the modification was
   dropped from the cherry-pick. The corresponding upgrade-guide entry for the
   4.14.x release line is added on `main` via a separate doc-sync PR targeting
   `camel-4x-upgrade-guide-4_14.adoc` (per the project's backport upgrade-guide
   policy).
   
   ### Sanity build
   
   - [x] `mvn clean install -DskipTests` from repo root on the backport worktree
         BUILD SUCCESS.
   
   ---
   
   _Claude Code (Opus 4.7) on behalf of @oscerd._


-- 
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