Skip to content

Add ES|QL to categorize-text challenge#712

Merged
jan-elastic merged 2 commits intomasterfrom
categorize-text-esql-2
Dec 13, 2024
Merged

Add ES|QL to categorize-text challenge#712
jan-elastic merged 2 commits intomasterfrom
categorize-text-esql-2

Conversation

@jan-elastic
Copy link
Contributor

No description provided.

@jan-elastic jan-elastic changed the base branch from categorize-text-esql to master December 13, 2024 09:22
@jan-elastic jan-elastic changed the title merge master Add ES|QL to categorize-text challenge Dec 13, 2024
@@ -1,5 +1,5 @@
{% import "rally.helpers" as rally %}
{% set shard_size_list = [10, 100, 1000] %}
{% set shard_size_list = [10, 100, 1000, 1000000000] %}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This "unlimited" shard_size is (currently) necessary to fairly compare ES|QL and query DSL, because ES|QL only supports unlimited shard_size.

Copy link
Contributor

@maxhniebergall maxhniebergall left a comment

Choose a reason for hiding this comment

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

LGTM

@jan-elastic jan-elastic merged commit 393ed97 into master Dec 13, 2024
@gareth-ellis gareth-ellis deleted the categorize-text-esql-2 branch August 18, 2025 16:00
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@jan-elastic
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!

@jan-elastic jan-elastic removed the backport pending Awaiting backport to stable release branch label Dec 22, 2025
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 23, 2025
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.

3 participants

Comments