Skip to content

[TSDB] Exclude index.block.write setting when creating rollup index#88812

Merged
csoulios merged 3 commits intoelastic:mainfrom
csoulios:copy-setting-index-block
Jul 26, 2022
Merged

[TSDB] Exclude index.block.write setting when creating rollup index#88812
csoulios merged 3 commits intoelastic:mainfrom
csoulios:copy-setting-index-block

Conversation

@csoulios
Copy link
Copy Markdown
Contributor

@csoulios csoulios commented Jul 26, 2022

PR #88565 modified the rollup action so that it copies all index settings from the source to the rollup index.
However, the rollup action expilitly requires that the source index has the index.block.write: true.

Since the rollup index must be writeable when it is created, this PR excludes the index.block.write index setting when creating the rollup index.

The index.block.write index setting is explictly set to true at the end of the rollup action (step 4).

@csoulios csoulios added >non-issue :StorageEngine/Rollup Turn fine-grained time-based data into coarser-grained data v8.4.0 labels Jul 26, 2022
@csoulios csoulios requested a review from nik9000 July 26, 2022 14:29
@elasticsearchmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-analytics-geo (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Jul 26, 2022
@csoulios csoulios changed the title [TSDB] Exclude index.block.write index setting when creating rollup index [TSDB] Exclude index.block.write setting when creating rollup index Jul 26, 2022
@csoulios csoulios merged commit 5f59c1c into elastic:main Jul 26, 2022
@csoulios csoulios deleted the copy-setting-index-block branch July 26, 2022 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :StorageEngine/Rollup Turn fine-grained time-based data into coarser-grained data Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants