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

   ## What
   
   Metadata hygiene in `camel-elasticsearch` and `camel-opensearch` (main only).
   
   ### 1. Wrong scroll-keep-alive header description
   The `CamelElasticsearchScrollKeepAliveMs` / 
`CamelOpensearchScrollKeepAliveMs` header (`PARAM_SCROLL_KEEP_ALIVE_MS`) was 
documented as **"The starting index of the response."** — a copy/paste from the 
from/offset header. It now describes the scroll keep-alive window, matching the 
`scrollKeepAliveMs` endpoint option.
   
   ### 2. Deprecate the unused `maxRetryTimeout` option
   The `maxRetryTimeout` endpoint and component option is never read — it is a 
leftover from the old low-level Elasticsearch REST client's 
`setMaxRetryTimeoutMillis`, which no longer exists in the client these 
components use today, so setting it has no effect. It is now `@Deprecated` 
(kept in place for backward compatibility of existing endpoint URIs) with an 
upgrade-guide note.
   
   ## Changes
   
   - `ElasticsearchConstants` / `OpensearchConstants`: corrected header 
description.
   - `Elasticsearch/Opensearch Configuration` + `Component`: `@Deprecated` on 
the `maxRetryTimeout` field and getters/setters; 
`@SuppressWarnings("deprecation")` on `createEndpoint` (which copies the option 
while it still exists).
   - Regenerated component metadata, catalog and endpoint/component DSL 
builders.
   - Upgrade-guide note in `camel-4x-upgrade-guide-4_23.adoc`.
   
   ## Notes
   
   - No functional/behaviour change; metadata + deprecation only.
   - Main only (deprecation + upgrade guide); not backported.
   
   _Generated by Claude Code on behalf of Andrea Cosentino (@oscerd)._
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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