-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ESQL: TopNOperator, release Row on failure #130330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Hi @GalLalouche, I've created a changelog YAML for you. |
| p = 0; | ||
| } | ||
|
|
||
| Row row = list.get(i); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line was basically moved to the try-with-resource clause. Everything else is indentation.
💔 Backport failed
You can use sqren/backport to manually backport by running |
Handles the case where the Row was released on failure, by moving the declaration to a try-with-resource clause. Resolves elastic#130215, elastic#130222, elastic#130270.
Handles the case where the Row was released on failure, by moving the declaration to a try-with-resource clause. Resolves elastic#130215, elastic#130222, elastic#130270.
Handles the case where the Row was released on failure, by moving the declaration to a try-with-resource clause. Resolves elastic#130215, elastic#130222, elastic#130270.
Resolves #130215, #130222, #130270.