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

(Doc+) Flush out Data Tiers #107981

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

(Doc+) Flush out Data Tiers #107981

wants to merge 9 commits into from

Commits on Apr 27, 2024

  1. (+Doc) Flush out Data Tiers

    πŸ‘‹πŸ½  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! πŸ™
    stefnestor committed Apr 27, 2024
    Configuration menu
    Copy the full SHA
    94d72a8 View commit details
    Browse the repository at this point in the history

Commits on May 2, 2024

  1. Grammar feedback

    Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
    stefnestor and shainaraskas committed May 2, 2024
    Configuration menu
    Copy the full SHA
    362201b View commit details
    Browse the repository at this point in the history
  2. _tier_preference section feedback

    Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
    stefnestor and shainaraskas committed May 2, 2024
    Configuration menu
    Copy the full SHA
    9eed70d View commit details
    Browse the repository at this point in the history
  3. Apply suggestions from code review

    Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
    stefnestor and shainaraskas committed May 2, 2024
    Configuration menu
    Copy the full SHA
    24035b3 View commit details
    Browse the repository at this point in the history

Commits on May 3, 2024

  1. Configuration menu
    Copy the full SHA
    955650a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    e6388c2 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    b71b016 View commit details
    Browse the repository at this point in the history
  4. Apply suggestions from code review

    Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
    stefnestor and shainaraskas committed May 3, 2024
    Configuration menu
    Copy the full SHA
    0b9ca75 View commit details
    Browse the repository at this point in the history

Commits on May 10, 2024

  1. Grammar feedback

    Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
    stefnestor and dakrone committed May 10, 2024
    Configuration menu
    Copy the full SHA
    c72d632 View commit details
    Browse the repository at this point in the history