-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Support migrating regular data streams to tsdb data streams #83520
Labels
:Data Management/Data streams
Data streams and their lifecycles
Team:Data Management
Meta label for data/management team
Comments
martijnvg
added
the
:Data Management/Data streams
Data streams and their lifecycles
label
Feb 4, 2022
Pinging @elastic/es-data-management (Team:Data Management) |
martijnvg
added a commit
to martijnvg/elasticsearch
that referenced
this issue
Feb 11, 2022
A regular data stream can be migrated to a tsdb data stream if the `index_mode` field is set to `time_series`. The `index_mode` field can only be update from null to `time_series`. Then on the next rollover the data stream's index mode's is changed from null to time_series and the new backing indices will have `index.mode` index setting set to `time_series` as well. Closes elastic#83520
martijnvg
added a commit
that referenced
this issue
Feb 17, 2022
A regular data stream can be migrated to a tsdb data stream if in template that created the data stream, the `index_mode` field is set to `time_series` and the data stream's `index_mode` property is either not specified or set to `standard`. Then on the next rollover the data stream is migrated to be a tsdb data stream. When that happens the data stream's `index_mode` property is set to `time_series` and the new backing index's `index.mode` index setting is also set to `time_series`. Closes #83520
probakowski
pushed a commit
to probakowski/elasticsearch
that referenced
this issue
Feb 23, 2022
…tic#83843) A regular data stream can be migrated to a tsdb data stream if in template that created the data stream, the `index_mode` field is set to `time_series` and the data stream's `index_mode` property is either not specified or set to `standard`. Then on the next rollover the data stream is migrated to be a tsdb data stream. When that happens the data stream's `index_mode` property is set to `time_series` and the new backing index's `index.mode` index setting is also set to `time_series`. Closes elastic#83520
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Data Management/Data streams
Data streams and their lifecycles
Team:Data Management
Meta label for data/management team
Migrating a regular data stream to be a tsdb data stream should be achieved by
setting the
index_mode
parameter totime_series
in the data stream snippetof the composable index template that created the data stream. This should only
be possible when no
index_mode
has been specified in the composable index template.When this change has been made to the composable index template, then the next
time the data stream rolls over the
index_mode
property of a data stream willbe set to
time_series
and a new backing index withindex.mode
index settingset
time_series
will be created. All new backing indices created by rolloverfor this migrated data stream will be tsdb indices.
The text was updated successfully, but these errors were encountered: