[Docs] Clarifying CSV limitations #175208
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Documentation preview: |
Dosant
added
release_note:skip
|
Pinging @elastic/appex-sharedux (Team:SharedUX) |
|
/ci |
💚 Build Succeeded
To update your PR or re-run it, just comment with: |
tsullivan
requested changes
Jan 23, 2024
| - Cross-cluster search is used | ||
| - ES|QL is used and result row count exceeds the limits of ES|QL queries | ||
|
|
||
| Use filters to create multiple smaller reports, or extract the data you need directly with the Elasticsearch APIs. See Point in time API, or SQL with CSV response data format. Reporting parameters can be adjusted to overcome some of these limiting scenarios. Results are dependent on data size, availability, and latency factors and are not guaranteed. |
There was a problem hiding this comment.
Suggested change
| Use filters to create multiple smaller reports, or extract the data you need directly with the Elasticsearch APIs. See Point in time API, or SQL with CSV response data format. Reporting parameters can be adjusted to overcome some of these limiting scenarios. Results are dependent on data size, availability, and latency factors and are not guaranteed. | |
| To work around the limitations, use filters to create multiple smaller reports, or extract the data you need directly with the Elasticsearch APIs. See Point in time API, or SQL with CSV response data format. Reporting parameters can be adjusted to overcome some of these limiting scenarios. Results are dependent on data size, availability, and latency factors and are not guaranteed. |
I think scroll should be included here as well, and the phrases should be linked.
Point-in-time API: https://www.elastic.co/guide/en/elasticsearch/reference/current/point-in-time-api.html
Scroll API: https://www.elastic.co/guide/en/elasticsearch/reference/current/scroll-api.html
SQL with CSV response: https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-rest-format.html
There was a problem hiding this comment.
Nice! I also added a link to reporting settings and mentioned ES|QL with csv response type
|
@elasticmachine merge upstream |
kibanamachine
added
v8.13.0
backport:skip
CoenWarmer
pushed a commit
to CoenWarmer/kibana
that referenced
this pull request
Feb 15, 2024
## Summary Adding CSV limitations section
amyjtechwriter
added a commit
that referenced
this pull request
Mar 22, 2024
Adding CSV limitations section and seeing if we can backport into 7.17x versions. It is a copy of #175208 which has been merged into 8.13. Let's see if this works 🤞 <img width="1184" alt="Screenshot 2024-03-22 at 09 24 50" src="https://github.com/elastic/kibana/assets/61687663/329b89a3-ec36-4dea-9983-b8ef441d0f2f"> --------- Co-authored-by: Kibana Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adding CSV limitations section as discussed here
https://kibana_175208.docs-preview.app.elstc.co/guide/en/kibana/master/reporting-getting-started.html