Skip to content

Conversation

@iverase
Copy link
Contributor

@iverase iverase commented Mar 17, 2025

No need to expend cycles and heap on it.

@iverase iverase added >non-issue :Search/Search Search-related issues that do not fall into other categories v9.0.0 v8.18.1 v8.19.0 v9.1.0 v8.17.4 labels Mar 17, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@elasticsearchmachine elasticsearchmachine added the Team:Search Meta label for search team label Mar 17, 2025
Copy link
Member

@benwtrent benwtrent left a comment

Choose a reason for hiding this comment

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

❤️

This should be marked as a bug IMO and this is a bug fix.

@iverase iverase added >bug and removed >non-issue labels Mar 17, 2025
@elasticsearchmachine
Copy link
Collaborator

Hi @iverase, I've created a changelog YAML for you.

@iverase
Copy link
Contributor Author

iverase commented Mar 17, 2025

Let's make it a bug then.

@javanna
Copy link
Member

javanna commented Mar 17, 2025

For the record, this change does not hurt and it's a good idea, but after #118266 , where we removed stacktraces for all exceptions returned back to the coord node, I am not so sure it's going to practically make a huge difference.

@javanna javanna added :Search Foundations/Search Catch all for Search Foundations and removed :Search/Search Search-related issues that do not fall into other categories labels Mar 17, 2025
@elasticsearchmachine elasticsearchmachine added Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch and removed Team:Search Meta label for search team labels Mar 17, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-foundations (Team:Search Foundations)

@iverase iverase added the auto-backport Automatically create backport pull requests when merged label Mar 17, 2025
@iverase iverase merged commit aba54e8 into elastic:main Mar 17, 2025
17 checks passed
@iverase iverase deleted the TaskCancelledException branch March 17, 2025 14:59
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.0
8.18
8.x
8.17 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 125002

iverase added a commit to iverase/elasticsearch that referenced this pull request Mar 17, 2025
iverase added a commit to iverase/elasticsearch that referenced this pull request Mar 17, 2025
iverase added a commit to iverase/elasticsearch that referenced this pull request Mar 17, 2025
iverase added a commit to iverase/elasticsearch that referenced this pull request Mar 17, 2025
# Conflicts:
#	modules/aggregations/src/internalClusterTest/java/org/elasticsearch/aggregations/bucket/SearchCancellationIT.java
elasticsearchmachine pushed a commit that referenced this pull request Mar 17, 2025
…125031)

* Don't generate stacktrace in TaskCancelledException (#125002)

# Conflicts:
#	modules/aggregations/src/internalClusterTest/java/org/elasticsearch/aggregations/bucket/SearchCancellationIT.java

* [CI] Auto commit changes from spotless

---------

Co-authored-by: elasticsearchmachine <[email protected]>
omricohenn pushed a commit to omricohenn/elasticsearch that referenced this pull request Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged >bug :Search Foundations/Search Catch all for Search Foundations Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v8.17.4 v8.18.1 v8.19.0 v9.0.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants