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

Saved objects management paging fails if paging past 10k saved objects #116776

Closed
rudolf opened this issue Oct 29, 2021 · 2 comments · Fixed by #118335
Closed

Saved objects management paging fails if paging past 10k saved objects #116776

rudolf opened this issue Oct 29, 2021 · 2 comments · Fixed by #118335
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Saved Objects Management impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@rudolf
Copy link
Contributor

rudolf commented Oct 29, 2021

When there are more than 10k saved objects, paging past the first 10k results result in the following error:

"all shards failed: search_phase_execution_exception: [illegal_argument_exception] Reason: Result window is too large, from + size must be less than or equal to: [10000] but was [19900]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting."

This is because saved objects management doesn't use a PIT/scroll search so results are limited to 10k.

I don't think it makes sense to page through more than 10k results, so I think we should just change the UI to say "only showing the first 10k results" similar to #82889

See related discussion about UI patterns elastic/eui#4506

Related #93505 #91562

@rudolf rudolf added bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Saved Objects Management labels Oct 29, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@azasypkin
Copy link
Member

azasypkin commented Nov 1, 2021

Just a few quick additional details, SO grid cannot also display counts of the SO types. The counts request fails because this same reason:

image


Export doesn't seem to work either:

curl 'https://kibana/s/space-a/api/saved_objects/_export' -X POST -H 'Content-Type: application/json' -H 'kbn-version: 7.16.0' --data-raw '{"type":[],"includeReferencesDeep":true}'

{"statusCode":400,"error":"Bad Request","message":"Either `type` or `objects` are required."}

@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Nov 1, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Nov 4, 2021
@pgayvallet pgayvallet self-assigned this Nov 11, 2021
@exalate-issue-sync exalate-issue-sync bot reopened this Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Saved Objects Management impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants