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
(Doc+) Flush out Data Tiers #107981
Open
stefnestor
wants to merge
9
commits into
main
Choose a base branch
from
stefnestor-patch-7
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
(Doc+) Flush out Data Tiers #107981
+108
β32
Commits on Apr 27, 2024
-
ππ½ howdy, team! I highly value the content on this [Data Tiers](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-tiers.html) page. Thanks for writing it! In my experience, some users may become slightly confused by its golden nuggets due to its brevity. This PR attempts to flush out common questions while remaining concise. The main changes are in the first and second-to-last sections; however, I do attempt some heading restructuring to make the TOC idea-groupings more clear for easier scan-throughs. The specific clarifications I'd like to push in order of appearance: - There's content tier (for "data category" > "content" as we've dubbed it on the higher page) and the data temperature tiers (for time series). That the temperature tiers group together is technically not stated so users end up asking about when they'd go hot>warm vs content>warm, etc. I suspect this confusion is only because users come straight to this page instead of starting at the hierarchy-parent page so have linked up. - (Main) Frozen being accessed/searched "rarely" should imply, well rarely. I wrote 1% in the PR `[TIP]` guideline section as a discussion starting point. Frequently we see users not understanding either that they actually have been or that they shouldn't have β₯25% of all searches hitting frozen tier. This comes up because of architecture bugs (e.g. frozen indices with future timestamps) but also just happenstance (e.g. 01605242 where of searches they hit majority hot, ~5% cold, but then again hit 75% frozen). - There's a slew of "how do I check that?", "how do I change that (at creation/later)?", "what if I set it null?" questions we get about `_tier_preference` so just extended the existing section already about it. TIA! π
Configuration menu - View commit details
-
Copy full SHA for 94d72a8 - Browse repository at this point
Copy the full SHA 94d72a8View commit details
Commits on May 2, 2024
-
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 362201b - Browse repository at this point
Copy the full SHA 362201bView commit details -
_tier_preference section feedback
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 9eed70d - Browse repository at this point
Copy the full SHA 9eed70dView commit details -
Apply suggestions from code review
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 24035b3 - Browse repository at this point
Copy the full SHA 24035b3View commit details
Commits on May 3, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 955650a - Browse repository at this point
Copy the full SHA 955650aView commit details -
Configuration menu - View commit details
-
Copy full SHA for e6388c2 - Browse repository at this point
Copy the full SHA e6388c2View commit details -
Configuration menu - View commit details
-
Copy full SHA for b71b016 - Browse repository at this point
Copy the full SHA b71b016View commit details -
Apply suggestions from code review
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 0b9ca75 - Browse repository at this point
Copy the full SHA 0b9ca75View commit details
Commits on May 10, 2024
-
Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for c72d632 - Browse repository at this point
Copy the full SHA c72d632View commit details
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.