(Doc+) Point ingest to Alias not Bootstrapped Index#107327
(Doc+) Point ingest to Alias not Bootstrapped Index#107327elasticsearchmachine merged 1 commit intomainfrom
Conversation
👋 @dakrone mentioned baby-update for docs. Sometimes users believe they should point client-side (e.g. Logstash's Elasticsearch output `index`) to the bootstrapped index. This highlights they point ingest towards the alias as we're expecting.
|
Documentation preview: |
|
@stefnestor please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
@stefnestor did you mean to merge this without any review? |
|
Uh, nope. Sorry. I meant it to auto-merge once approved, @dakrone . |
| You can search across all of the data stream's backing indices, managed by the `timeseries_policy`, | ||
| with the `timeseries` data stream name. | ||
| Write operations are routed to the current write index. Read operations will be handled by all | ||
| You will point ingest towards the alias which will route write operations to its current write index. Read operations will be handled by all |
There was a problem hiding this comment.
This is confusing, because in this section, this is about creating the data stream, and there is no "alias" in play. It should read instead something like:
"Write operations should be sent to the data stream name, which will route them to its current write index. Read operations on the data stream will be handled by all backing indices."
|
@stefnestor okay, the |
|
For sure, sorry about that! I was label copying from your #107233 but didn't realize the two labels separate worked different than them together (or maybe that's a Lead-only thing). But on what to fix, from the doc you updated it links to Manage time series data without data streams which links to Bootstrap the initial time series index with a write index alias which wouldn't be DataStreams within that context. Maybe instead ...
|
Can you open a new PR and we can work through this there? |
👋 @dakrone mentioned baby-update for docs. Sometimes users believe they should point client-side (e.g. Logstash's Elasticsearch output `index`) to the bootstrapped index. This highlights they point ingest towards the alias as we're expecting.
👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts?
* (Doc+) Delineate Bootstrapping Data Stream from Alias 👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts? * Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
* (Doc+) Delineate Bootstrapping Data Stream from Alias 👋 howdy, team! This is follow-up to [elasticsearch#107327](elastic#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts? * Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> (cherry picked from commit a3f3f59)
) * (Doc+) Delineate Bootstrapping Data Stream from Alias 👋 howdy, team! This is follow-up to [elasticsearch#107327](#107327). I realized my mistake was that we had duplicate sentences in different sections so I edited the wrong area. However, it seemed like a good opportunity to consider clarifying the page better by fixing header links so that the sub-sections reflect as sub-headers instead of all being equal. Thoughts? * Apply suggestions from code review Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --------- Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> (cherry picked from commit a3f3f59) Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
👋 howdy, team!
Sometimes users believe they should point client-side (e.g. Logstash's Elasticsearch output
index) to the bootstrapped index. This highlights they point ingest towards the alias.cc: @dakrone