You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: