oscerd opened a new pull request, #23212: URL: https://github.com/apache/camel/pull/23212
## Summary Rename the string values of the `ElasticSearchRestClientConstant` Exchange header constants to follow the `CamelElasticsearch*` prefix used by every other component in the catalog (`CamelSqlQuery`, `CamelMongoDbCriteria`, `CamelCqlQuery`, etc.). Java field names are unchanged - only the 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 ## Changes - `ElasticSearchRestClientConstant.java`: rename the five header constant values to the `CamelElasticsearch*` prefix. - `elasticsearch-rest-client-component.adoc`: update narrative text and Java DSL examples to reference the new header names. - `camel-4x-upgrade-guide-4_21.adoc`: add a section documenting the rename, the affected constants, and the migration path for routes that set the header by literal string. - Regenerated downstream artifacts (component catalog mirror, component JSON metadata, endpoint DSL builder). Routes that reference the constants symbolically (`ElasticSearchRestClientConstant.SEARCH_QUERY`, etc.) continue to work without changes. Routes that hard-code the literal `"SEARCH_QUERY"` (or the other old values) need to switch to the new strings. ## Test plan - [x] `mvn verify` in `components/camel-elasticsearch-rest-client` - integration tests pass (2/2). - [x] Full reactor `mvn clean install -DskipTests` from repo root - BUILD SUCCESS. All regen artifacts related to this change committed; unrelated stale regen (jbang configuration metadata) reverted. - [ ] CI green. --- _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]
