Merged
Conversation
dnhatn
added
:Analytics/ES|QL
Collaborator
|
Hi @dnhatn, I've created a changelog YAML for you. |
elasticsearchmachine
added
the
Team:Analytics
Collaborator
|
Hi @dnhatn, I've updated the changelog YAML for you. |
Collaborator
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
Member
Author
|
Thanks Chris! |
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
szybia
added a commit
to szybia/elasticsearch
that referenced
this pull request
Mar 2, 2026
…locations
* upstream/main: (94 commits)
Mute org.elasticsearch.xpack.esql.qa.mixed.EsqlClientYamlIT test {p0=esql/40_tsdb/TS Command grouping on text field} elastic#142544
Mute org.elasticsearch.index.store.StoreDirectoryMetricsIT testDirectoryMetrics elastic#143419
Mute org.elasticsearch.xpack.esql.qa.multi_node.GenerativeIT test elastic#143023
TS_INFO information retrieval command (elastic#142721)
ESQL: External source parallel execution and distribution (elastic#143349)
Mute org.elasticsearch.index.mapper.blockloader.FlattenedFieldRootBlockLoaderTests testBlockLoaderForFieldInObject {preference=Params[syntheticSource=false, preference=DOC_VALUES]} elastic#143414
Mute org.elasticsearch.index.mapper.blockloader.FlattenedFieldRootBlockLoaderTests testBlockLoaderForFieldInObject {preference=Params[syntheticSource=false, preference=NONE]} elastic#143413
Mute org.elasticsearch.index.mapper.blockloader.FlattenedFieldRootBlockLoaderTests testBlockLoaderForFieldInObject {preference=Params[syntheticSource=false, preference=STORED]} elastic#143412
Removing ingest random sampling (elastic#143289)
Mute org.elasticsearch.xpack.esql.qa.single_node.GenerativeIT test elastic#143023
[Transform] Clean up internal tests (elastic#143246)
Skip time series field type merge for non-TS agg queries (elastic#143262)
Enable zero-copy SIMD vector scoring on searchable snapshots (frozen tier) (elastic#141718)
Mute org.elasticsearch.xpack.search.CrossClusterAsyncSearchIT testCancelViaExpirationOnRemoteResultsWithMinimizeRoundtrips elastic#143407
Fix MemorySegmentUtilsTests (elastic#143391)
Unmute testWorkflowsRestrictionAllowsAccess (elastic#143308)
Cancel async query on expiry (elastic#143016)
ESQL: Finish migrating error testing (elastic#143322)
Reduce LuceneOperator.Status memory consumption with large QueryDSL queries (elastic#143175)
ESQL: Generative testing with full text functions (elastic#142961)
...
tballison
pushed a commit
to tballison/elasticsearch
that referenced
this pull request
Mar 3, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes elastic#142662
This was referenced Mar 6, 2026
|
Hi, @dnhatn . Could you please confirm whether or not this PR was or will be backported to 9.3.2? Our customer had been waiting for this bug fix, and we said it would be available in 9.3.2 per the labels on this PR. However, this comment states that the backport failed, and I don't see the fix for it listed in the 9.3.2 release notes: https://www.elastic.co/docs/release-notes/elasticsearch#elasticsearch-9.3.2-release-notes |
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes elastic#142662 (cherry picked from commit 8feeac8)
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes elastic#142662 (cherry picked from commit 8feeac8)
Member
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
dnhatn
added
v9.3.3
v9.2.8
v8.19.14
and removed
backport pending
v9.3.2
v9.2.7
v8.19.13
labels
dnhatn
added a commit
to dnhatn/elasticsearch
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes elastic#142662 (cherry picked from commit 8feeac8)
Member
Author
|
@jsevidal13 I'm so sorry; I missed the backport, and this fix unfortunately did not make it into 9.3.2. I am backporting it now, and it should be available in 9.3.3. |
dnhatn
added a commit
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes #142662 (cherry picked from commit 8feeac8)
dnhatn
added a commit
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes #142662 (cherry picked from commit 8feeac8)
dnhatn
added a commit
that referenced
this pull request
Mar 24, 2026
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get. Closes #142662 (cherry picked from commit 8feeac8)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Today, we don’t cancel async queries when they expire. This means an async query continues running until it completes, unless the user explicitly deletes it. With this change, we will schedule a cancellation when an async query starts and reschedule the cancellation whenever the keep-alive is updated via get.
Closes #142662