-
Couldn't load subscription status.
- Fork 25.6k
Gate disable norms on text fields for logsdb/tsdb indices #133493
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
Conversation
|
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
|
Hi @Kubik42, I've created a changelog YAML for you. |
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.
One nit, otherwise LGTM!
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. Thanks @Kubik42
The template that this test suite creates was never used during the test. This is because it uses default priority, and the builtin `logs@template` which also matches with the data stream name has a higher priority. This change addresses this problem by setting the priority to 200 for the template that this test suite creates. Additionally, an extra check is added the verifying that the created template is actually used by the data stream that this test suite creates. This change results in this test suite to fail if elastic#133493 isn't applied.
The template that this test suite creates was never used during the test. This is because it uses default priority, and the builtin `logs@template` which also matches with the data stream name has a higher priority. This change addresses this problem by setting the priority to 200 for the template that this test suite creates. Additionally, an extra check is added the verifying that the created template is actually used by the data stream that this test suite creates. This change results in this test suite to fail if #133493 isn't applied.
#131317 is blocking serverless deployments because Lucene doesn't allow norms to be changed, and since we're changing them, we end up hitting the following Lucene bug.
Our docs and code need to be updated since we document that norms can be disabled (true -> false). This doesn't align with that Lucene has. I will follow up with another PR to update them.