-
Notifications
You must be signed in to change notification settings - Fork 0
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
Show actual number of table pages #243
Comments
I tried to just set the tracking number to Integer.MAX_VALUE which seems to work at first (after also setting this to the ES index because it also has a default cutoff at 10k and will return an error). However, the returned count in GePI does not correspond to the count of the same query when I send it to ES via cerebro (direct JSON API usage) but is ca. twice as large. The effect of this are errors when trying to jump to the end. Also, we'd like accurate numbers. Investigate. |
The issue was that the elasticsearch query components failed to set the index on the search request which led to a search across all indices. Since a second, clean index was built at that time, there were nearly as twice results. |
Decided to leave the 10k restriction on the table. The total number of events is given in the statistics, who need the complete table can download it. There is no reason why the 1000th page is worse than the 2000th page. |
And do not cut at 10k. The cutoff ought to save time but in my tests with GePI its not much of a difference and the more specific information is better.
The text was updated successfully, but these errors were encountered: