Skip to content

Comments

[ES|QL] Add new queries into nyc_taxis track to measure DateTrunc to RoundTo transformation#824

Merged
fang-xing-esql merged 3 commits intoelastic:masterfrom
fang-xing-esql:datetrunc-to-roundto
Jul 24, 2025
Merged

[ES|QL] Add new queries into nyc_taxis track to measure DateTrunc to RoundTo transformation#824
fang-xing-esql merged 3 commits intoelastic:masterfrom
fang-xing-esql:datetrunc-to-roundto

Conversation

@fang-xing-esql
Copy link
Member

Add 3 new date_histogram queries with different calendar intervals to nyc_taxis track to measure performance improvements related to filter-by-filter aggregation in ES|QL, it is related to elastic/elasticsearch#131341 and elastic/elasticsearch#128639

@fang-xing-esql fang-xing-esql added the new workload Any work related to adding a new track or functionality within a track label Jul 22, 2025
Copy link
Member

@nik9000 nik9000 left a comment

Choose a reason for hiding this comment

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

They'd be useful for me if we have the space for them.

Copy link
Member

@inqueue inqueue left a comment

Choose a reason for hiding this comment

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

LGTM

@fang-xing-esql
Copy link
Member Author

Thanks for reviewing @nik9000 @inqueue !

@fang-xing-esql fang-xing-esql merged commit 1658376 into elastic:master Jul 24, 2025
14 checks passed
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@fang-xing-esql
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!

@esbenchmachine
Copy link
Collaborator

💔 All backports failed

Status Branch Result
9.2 Backport failed because of merge conflicts
9.3 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 824

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@esbenchmachine
Copy link
Collaborator

💔 All backports failed

Status Branch Result
9.2 Backport failed because of merge conflicts
9.3 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 824

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

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 new workload Any work related to adding a new track or functionality within a track v9.2 v9.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants