Skip to content

Comments

Reset#52

Merged
NickDris merged 11 commits intomasterfrom
reset
Sep 15, 2025
Merged

Reset#52
NickDris merged 11 commits intomasterfrom
reset

Conversation

@NickDris
Copy link
Owner

No description provided.

Update the so_vector rally track to also exercise knn against the ESQL frontend.
Add patterned_text_index_options parameter to elastic/log tracks. Can accepts value of docs and positions, defaults to docs. Sets the index_options value of the message field in all indices. Only applies if patterned_text_message_field is set to true, and message fields are patterned_text, rather than match_only_text.
Add challenge which queries message field with several term and phrase queries. This is meant to test the patterned_text mapping type, but can also be used to test match_only_text message fields.
Setting this is not necessary as the routing path is set automatically for data streams and this template defines `"data_stream": {}`. It would also prevent an optimization added in elastic/elasticsearch#132566.
Rolls back changes in elastic#722 that broke the `ingest_mode: data_stream`.
@github-actions
Copy link

The label indicates that this pull request requires backporting. Please review next steps for backporting.

@NickDris NickDris merged commit d8ccb77 into master Sep 15, 2025
2 of 13 checks passed
@NickDris NickDris deleted the reset branch September 15, 2025 08:16
@NickDris NickDris added backport pending Awaiting backport to stable release branch and removed backport-pending backport pending Awaiting backport to stable release branch labels Oct 23, 2025
@NickDris NickDris added backport pending Awaiting backport to stable release branch and removed backport pending Awaiting backport to stable release branch labels Dec 12, 2025
@NickDris
Copy link
Owner Author

@NickDris
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants