Open
Description
The es archiver load action is being updated to increase speed.
The usual culprit is the concurrency, which places data out of expected sort order.
We expect placing a sort order in the queries themselves is one solution.
Another could be asserting in such a fashion that does not require a sort order.
This is issue is an attempt to ensure that no decreased coverage, goes overlooked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment