-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Fix multi fields in downsampling #138869
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
Fix multi fields in downsampling #138869
Conversation
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
|
Hi @gmarouli, I've created a changelog YAML for you. |
martijnvg
left a comment
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 👍
💔 Backport failed
You can use sqren/backport to manually backport by running |
(cherry picked from commit 5918605) # Conflicts: # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/AggregateSubMetricFieldValueFetcher.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/DownsampleShardIndexer.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/FieldValueFetcher.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/RestDownsampleAction.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/TransportDownsampleAction.java
(cherry picked from commit 5918605) # Conflicts: # server/src/main/resources/transport/upper_bounds/9.2.csv # server/src/main/resources/transport/upper_bounds/9.3.csv # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/AggregateSubMetricFieldValueFetcher.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/DownsampleShardIndexer.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/FieldValueFetcher.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/RestDownsampleAction.java # x-pack/plugin/downsample/src/main/java/org/elasticsearch/xpack/downsample/TransportDownsampleAction.java # x-pack/plugin/downsample/src/test/java/org/elasticsearch/xpack/downsample/DownsampleShardPersistentTaskExecutorTests.java
💔 Some backports could not be created
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
In #138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp".
…tic#139104) In elastic#138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp". (cherry picked from commit 47698be) # Conflicts: # x-pack/plugin/downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
…tic#139104) In elastic#138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp". (cherry picked from commit 47698be) # Conflicts: # x-pack/plugin/downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
…139111) In #138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp". (cherry picked from commit 47698be) # Conflicts: # x-pack/plugin/downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
…139114) In #138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp". (cherry picked from commit 47698be) # Conflicts: # x-pack/plugin/downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
…139118) In #138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp". (cherry picked from commit 47698be) # Conflicts: # x-pack/plugin/downsample/src/internalClusterTest/java/org/elasticsearch/xpack/downsample/DownsampleIT.java
…tic#139104) In elastic#138869 we fixed the handling of the multi-fields; however, we introduced a bug when a mapping contains a alias type. For example, the following mapping: ``` "@timestamp": { "type": "date" }, "timestamp": { "type": "alias", "path": "@timestamp" } ``` The cause of the bug was that in the `FieldValueFetcher` we switch the check wether a field is indexed from the name we retrieved in the label to the name of the field type. In this case, the label is `timestamp` which does not in the indexed but the name of the field type is "@timestamp".
Recently, we identified certain edge cases when downsampling multi-fields: