-
Notifications
You must be signed in to change notification settings - Fork 441
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
[System][Core] Add dimensions for the core data_stream #6454
[System][Core] Add dimensions for the core data_stream #6454
Conversation
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
🌐 Coverage report
|
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
…a_stream Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
@@ -2,7 +2,8 @@ | |||
type: group | |||
fields: | |||
- name: id | |||
type: keyword | |||
type: long |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this field is of type long
in mericbeat - https://github.com/elastic/beats/blob/main/metricbeat/module/system/core/_meta/fields.yml#L1-L10
enablement of TSDB does not work in case of using keyword due to this issue - elastic/elasticsearch#96552
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this change be a breaking change?
An alternative option, having minimal impact which can be considered is to introduce a new field , say core_long_id
or similar having type long
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this change be a breaking change?
I don't think that this should be considered as breaking change, @lalit-satapathy please correct me if I am wrong
An alternative option, having minimal impact which can be considered is to introduce a new field , say core_long_id or similar having type long.
I think it is better to wait than this fix - elastic/elasticsearch#96552 than introducing, then deprecating and removing a redundant field, used just to set a dimension
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NOTE: as agreed in elastic/elasticsearch#96552 (comment), by d4910e7 commit:
- do not enable tsdb on this data_stream
- revert core.id type back to keyword
@agithomas could you please review this PR again?
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
…id type to keyword Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
/test |
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Package system - 1.34.1 containing this change is available at https://epr.elastic.co/search?package=system |
What does this PR do?
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots