Skip to content
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

Call updateState when query is cancelled #3139

Merged
merged 2 commits into from
Oct 30, 2024

Conversation

ykmr1224
Copy link
Collaborator

@ykmr1224 ykmr1224 commented Oct 29, 2024

Description

  • Call updateState when query is cancelled
    • This change is for async-query-core library consumer to update cancel status
    • This does not affect the async-query behavior since AsyncQueryJobMetadata record does not store status yet. ([FEATURE] Unify the async query request metadata model #3140 is an issue for unifying the model to single one, and we need to handle the update status within the fix)

Related Issues

#3140 (This PR does not solve this issue)

Check List

  • New functionality includes testing.
  • New functionality has been documented.
  • New functionality has javadoc added.
  • New functionality has a user manual doc added.
  • API changes companion pull request created.
  • Commits are signed per the DCO using --signoff.
  • Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Tomoyuki Morita <[email protected]>
@noCharger
Copy link
Collaborator

This does not affect the async-query behavior since AsyncQueryJobMetadata record does not store status yet

It makes me feel like this PR is a short term solution, is it an urgent change or we can go with longer term approach #3140?

@ykmr1224
Copy link
Collaborator Author

This does not affect the async-query behavior since AsyncQueryJobMetadata record does not store status yet

It makes me feel like this PR is a short term solution, is it an urgent change or we can go with longer term approach #3140?

Yes, this is short term, but it does not have side effect. #3140 require much more effort and we don't have bandwidth right now.

@ykmr1224 ykmr1224 merged commit 5716cab into opensearch-project:main Oct 30, 2024
14 of 15 checks passed
@ykmr1224 ykmr1224 added the maintenance Improves code quality, but not the product label Oct 31, 2024
opensearch-trigger-bot bot pushed a commit that referenced this pull request Oct 31, 2024
* Call updateState when query is cancelled

Signed-off-by: Tomoyuki Morita <[email protected]>

* Fix code style

Signed-off-by: Tomoyuki Morita <[email protected]>

---------

Signed-off-by: Tomoyuki Morita <[email protected]>
(cherry picked from commit 5716cab)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
ykmr1224 pushed a commit that referenced this pull request Oct 31, 2024
* Call updateState when query is cancelled



* Fix code style



---------


(cherry picked from commit 5716cab)

Signed-off-by: Tomoyuki Morita <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x maintenance Improves code quality, but not the product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants