Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network-safe scroll API #61449

Closed
pauldraper opened this issue Aug 23, 2020 · 2 comments
Closed

Network-safe scroll API #61449

pauldraper opened this issue Aug 23, 2020 · 2 comments
Labels
:Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team

Comments

@pauldraper
Copy link

Currently, if there is a network error, the scroll API must be restarted, to prevent records from being missed.

This is inconvenient when iterating over millions of records to do maintenance (e.g. sync with another source).

Perhaps the solution is separate the fetch and advance operations of the scroll API, so that consumers could confirm reception of hits before advancing.

@pauldraper pauldraper added >enhancement needs:triage Requires assignment of a team area label labels Aug 23, 2020
@dnhatn
Copy link
Member

dnhatn commented Aug 24, 2020

I am closing this as we already have an issue for this enhancement. Thank you very much for your interest in Elasticsearch.

Duplicates of #26472

@dnhatn dnhatn closed this as completed Aug 24, 2020
@dnhatn dnhatn added :Search/Search Search-related issues that do not fall into other categories and removed >enhancement needs:triage Requires assignment of a team area label labels Aug 24, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Search)

@elasticmachine elasticmachine added the Team:Search Meta label for search team label Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team
Projects
None yet
Development

No branches or pull requests

3 participants