oscerd opened a new pull request, #23538:
URL: https://github.com/apache/camel/pull/23538
Backports #23442 to `camel-4.18.x`.
Cherry-pick of merge commit `70d9e92ee03` with one adaptation: the original
PR's upgrade-guide entry was added to `camel-4x-upgrade-guide-4_21.adoc`,
which does not exist on the 4.18.x maintenance branch. Per the project's
backport policy the same content has been added to
`camel-4x-upgrade-guide-4_18.adoc` instead.
## Summary
Renames the `PARAM_*` Exchange header string values in
`ElasticsearchConstants`
and `OpensearchConstants` that were **not** in the `Camel` namespace to
`CamelElasticsearch*` / `CamelOpensearch*` respectively.
10 constants renamed in `ElasticsearchConstants` (`PARAM_OPERATION`,
`PARAM_INDEX_ID`, `PARAM_INDEX_NAME`, `PARAM_DOCUMENT_CLASS`,
`PARAM_WAIT_FOR_ACTIVE_SHARDS`, `PARAM_SCROLL_KEEP_ALIVE_MS`, `PARAM_SCROLL`,
`PARAM_SIZE`, `PARAM_FROM`, `PARAM_DOCUMENT_MODE`); 9 constants renamed in
`OpensearchConstants` (same minus `PARAM_DOCUMENT_MODE`, which only exists in
`ElasticsearchConstants`).
The Java field names are unchanged so routes referencing the constants
symbolically continue to work; routes using the literal string values must be
updated. `PROPERTY_SCROLL_ES_QUERY_COUNT` /
`PROPERTY_SCROLL_OPENSEARCH_QUERY_COUNT` were already `Camel`-prefixed and
are unchanged.
DSL accessors renamed accordingly: `operation()` → `elasticsearchOperation()`
/ `opensearchOperation()`, `indexId()` → `elasticsearchIndexId()` /
`opensearchIndexId()`, etc.
## Test plan
- [x] `mvn test` in `components/camel-elasticsearch` on 4.18.x — BUILD
SUCCESS
- [x] `mvn test` in `components/camel-opensearch` on 4.18.x — BUILD SUCCESS
- [x] Cherry-pick applied cleanly except for the 4_21 → 4_18 guide-file
rename described above (no merge marker shipped)
- [x] Upgrade-guide entry added under
`=== camel-elasticsearch / camel-opensearch - potential breaking
change`
in `camel-4x-upgrade-guide-4_18.adoc`
Tracker: CAMEL-23577
_Reported by 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]
