-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix PerFieldFormatSupplier mistake #134008
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 PerFieldFormatSupplier mistake #134008
Conversation
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
Correctly use seqno_field_use_tsdb_doc_values_format feature flag to ensure _seq_no doesn't get excluded.
return fieldName.startsWith("_") | ||
&& fieldName.equals("_tsid") == false | ||
&& fieldName.equals("_ts_routing_hash") == false | ||
&& (SEQNO_FIELD_USE_TSDB_DOC_VALUES_FORMAT.isEnabled() && fieldName.equals(SeqNoFieldMapper.NAME) == false); |
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.
Checking whether feature flag is enabled and whether seqno should not be excluded can't be expressed this way. Because if feature flag is disabled this then results in the field not being excluded.
f8c9bdb
to
499bef6
Compare
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 Martijn!
…doc_values_format_ff
if (SEQNO_FIELD_USE_TSDB_DOC_VALUES_FORMAT.isEnabled()) { | ||
includeMetaField.add(SeqNoFieldMapper.NAME); | ||
} | ||
// Don't include _recovery_source_size and _recovery_source since their values can be filtered out in |
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 comment is off?
argh but jobs fail with:
Not sure why. |
…doc_values_format_ff
…doc_values_format_ff
…doc_values_format_ff
…doc_values_format_ff
Correctly use seqno_field_use_tsdb_doc_values_format feature flag to ensure _seq_no doesn't get excluded.
Marking as non-issue as this would only be a bug in a released stateful release.
Closes #133875
Closes #133993