Skip to content

Conversation

martijnvg
Copy link
Member

@martijnvg martijnvg commented Sep 2, 2025

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

@elasticsearchmachine
Copy link
Collaborator

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);
Copy link
Member Author

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.

@martijnvg martijnvg force-pushed the fix_seqno_field_use_tsdb_doc_values_format_ff branch from f8c9bdb to 499bef6 Compare September 2, 2025 18:24
@martijnvg martijnvg requested review from dnhatn and kkrik-es September 2, 2025 18:25
Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks Martijn!

@dnhatn dnhatn enabled auto-merge (squash) September 2, 2025 19:03
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This comment is off?

@martijnvg
Copy link
Member Author

argh but jobs fail with:

* What went wrong:
Execution failed for task ':build-tools:javadoc'.
> Javadoc generation failed. Generated Javadoc options file (useful for troubleshooting): '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1756883074995710979/elastic/elasticsearch-pull-request/build-tools/build/tmp/javadoc/javadoc.options'

Not sure why.

@dnhatn dnhatn merged commit 5e7159e into elastic:main Sep 3, 2025
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CI] LogsIndexingIT testRouteOnSortFields failing [CI] LogsIndexingIT failing, DirectMonotonicWriter reports wrong number of values added

4 participants