You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2026/09/18 11:24:00 UTC

[jira] [Resolved] (CAMEL-24817) camel-elasticsearch/camel-opensearch: fix scroll-keep-alive header description and deprecate the unused maxRetryTimeout option

     [ https://issues.apache.org/jira/browse/CAMEL-24817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino resolved CAMEL-24817.
--------------------------------------
    Resolution: Fixed

> camel-elasticsearch/camel-opensearch: fix scroll-keep-alive header description and deprecate the unused maxRetryTimeout option
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-24817
>                 URL: https://issues.apache.org/jira/browse/CAMEL-24817
>             Project: Camel
>          Issue Type: Task
>          Components: camel-elasticsearch, camel-opensearch
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.23.0
>
>
> Metadata hygiene in both components (main only):
> *1. Wrong header description.* The {{CamelElasticsearchScrollKeepAliveMs}} / {{CamelOpensearchScrollKeepAliveMs}} header ({{PARAM_SCROLL_KEEP_ALIVE_MS}}) is documented as _"The starting index of the response."_ - a copy/paste from the from/offset header. It should describe the scroll keep-alive window, matching the {{scrollKeepAliveMs}} endpoint option ("Time in ms during which Elasticsearch/OpenSearch will keep the search context alive").
> *2. Dead maxRetryTimeout option.* The {{maxRetryTimeout}} {{@UriParam}} (and the matching component option) is never read anywhere - it is a leftover from the old low-level Elasticsearch RestClient's {{setMaxRetryTimeoutMillis}}, which no longer exists in the current client. Setting it has no effect. Deprecate it (component + configuration getters/setters) so users are warned, and add an upgrade-guide note. It is left in place rather than removed to preserve backward compatibility of existing endpoint URIs.
> Regenerates component metadata/docs/catalog. Main only (deprecation + upgrade-guide); not backported.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)