Skip to content

Add FlattenedFieldBinaryVsSortedSetDocValuesSyntheticSourceIT#140489

Merged
jordan-powers merged 3 commits intoelastic:mainfrom
jordan-powers:flattened-field-binary-vs-sorted-set-test
Jan 12, 2026
Merged

Add FlattenedFieldBinaryVsSortedSetDocValuesSyntheticSourceIT#140489
jordan-powers merged 3 commits intoelastic:mainfrom
jordan-powers:flattened-field-binary-vs-sorted-set-test

Conversation

@jordan-powers
Copy link
Contributor

This PR adds a test to compare the synthetic source produced by flattened fields using the TSDB codec against flattened fields not using that codec. The test generates 32 random documents, indexes them into two indices (one using the codec, the other not using the codec), then retrieves the documents from the two indices and compares them.

This is a test for #140246, since once that PR is merged, flattened fields using the TSDB codec will use binary doc values while flattened fields using the default codec will continue to use sorted set doc values.

This PR adds a test to compare the synthetic source produced by flattened
fields using the TSDB codec against flattened fields not using that
codec. The test generates 32 random documents, indexes them into two
indices (one using the codec, the other not using the codec), then
retrieves the documents from the two indices and compares them.

This is a test for elastic#140246, since once that PR is merged, flattened
fields using the TSDB codec will use binary doc values while flattened
fields using the default codec will continue to use sorted set doc
values.
@jordan-powers jordan-powers self-assigned this Jan 10, 2026
@jordan-powers jordan-powers added >test Issues or PRs that are addressing/adding tests :StorageEngine/Mapping The storage related side of mappings labels Jan 10, 2026
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-storage-engine (Team:StorageEngine)

Copy link
Member

@martijnvg martijnvg left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@jordan-powers jordan-powers merged commit 5b0e97e into elastic:main Jan 12, 2026
35 checks passed
@jordan-powers jordan-powers deleted the flattened-field-binary-vs-sorted-set-test branch January 12, 2026 16:01
szybia added a commit to szybia/elasticsearch that referenced this pull request Jan 12, 2026
…i-project-tests

* upstream/main: (23 commits)
  Fix `testAckListenerReceivesNacksIfPublicationTimesOut` (elastic#140514)
  Reduce priority of clear-cache tasks (elastic#139685)
  Add docs and tests about `StreamOutput` to memory (elastic#140365)
  ES|QL - dense_vector support for COUNT, PRESENT, ABSENT aggregator functions (elastic#139914)
  Add release notes for v9.2.4 release (elastic#140487)
  Add release notes for v9.1.10 release (elastic#140488)
  Add conncectors release notes for 9.1.10, 9.2.4 (elastic#140499)
  Add parameter support in PromQL query durations (elastic#139873)
  Improve testing of STS credentials reloading (elastic#140114)
  Fix zstd native binary publishing script to support newer versions (elastic#140485)
  Add FlattenedFieldBinaryVsSortedSetDocValuesSyntheticSourceIT (elastic#140489)
  Store fallback match only text fields in binary doc values (elastic#140189)
  [DiskBBQ] Use the new merge executor for intra-merge parallelism (elastic#139942)
  ESQL: introduce support for mapping-unavailable fields (elastic#140463)
  Add ESNextOSQVectorsScorerTests (elastic#140436)
  Disable high cardinality tests on release builds (elastic#140503)
  ESQL: TRange timezone support (elastic#139911)
  Directly compressing `StreamOutput` (elastic#140502)
  ES|QL - fix dense vector enrich bug (elastic#139774)
  Use CrossProjectModeDecider in RemoteClusterService (elastic#140481)
  ...
spinscale pushed a commit to spinscale/elasticsearch that referenced this pull request Jan 21, 2026
…c#140489)

This PR adds a test to compare the synthetic source produced by flattened
fields using the TSDB codec against flattened fields not using that
codec. The test generates 32 random documents, indexes them into two
indices (one using the codec, the other not using the codec), then
retrieves the documents from the two indices and compares them.

This is a test for elastic#140246, since once that PR is merged, flattened
fields using the TSDB codec will use binary doc values while flattened
fields using the default codec will continue to use sorted set doc
values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:StorageEngine/Mapping The storage related side of mappings Team:StorageEngine >test Issues or PRs that are addressing/adding tests v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants