-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Reporting] Fix incorrect number of hits being exported from CSV #112406
Conversation
@elasticmachine merge upstream |
I looked back in the PR branch that added the current CSV export implementation: #88303. In the first commit / original implementation, the plan was to use PIT instead of the ES |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Summary
Fix #112164
The following was being reported for subsequent runs of a large CSV export on CI. TL;DR, the CSV row count was random, but always below the expected 4675 total.
Data
It appears that this was reproducible only with using the
_scroll
endpoint. After switching to using point in time per the recommendation in the docs, we are getting consistent CSV row counts again:The docs indicate that scroll should not be used to span more than 10000 docs, but in this case we were spanning less than half that. We should do an analysis to determine how far back this was introduced as it is likely a result of something in ES changing (still investigating).
How to test locally
(this can be automated by running the functional test
generates a report from a new search with data: default
)x-pack/test/functional/es_archives/reporting/ecommerce
Release note
Does this need a public release note?
Checklist