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

Correctly terminate the explore command #2120

Merged
merged 2 commits into from
Mar 6, 2022
Merged

Conversation

tobim
Copy link
Member

@tobim tobim commented Feb 27, 2022

This commit fixes 2 issues that prevented the exporter for the initial query from exiting.

  • When the explorer received the requested number of results for the initial query it did not communicate this to the exporter, causing the latter to wait for a follow-up request indefinitely.
  • When the max-events-query * max-events-context was lower than max-events the sink would wait for additional results but the explorer would only wait to get terminated.

📝 Checklist

  • All user-facing changes have changelog entries.
  • The PR description contains instructions for the reviewer, if necessary.

🎯 Review Instructions

Run an explore command on a database with more than 5 partitions and an initial query with a low selectivity.

@tobim tobim added the bug Incorrect behavior label Feb 27, 2022
@tobim tobim requested a review from lava February 27, 2022 19:47
Copy link
Member

@lava lava left a comment

Choose a reason for hiding this comment

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

The fix makes sense to me.

tobim added 2 commits March 1, 2022 17:57
This commit fixes 2 issues that prevented the exporter for the initial
query from exiting.
When the explorer received the requested number of results for the
initial query it did not communicate this to the exporter, causing the
latter to wait for a follow-up request indefinitely.
When the `max-events-query * max-events-context` was lower than
`max-events` the sink would wait for additional results but the `explorer`
would only wait to get terminated.
@tobim tobim force-pushed the topic/fix-explorer-shutdown branch from 0a29187 to e558403 Compare March 1, 2022 17:07
@tobim tobim merged commit ad71871 into master Mar 6, 2022
@tobim tobim deleted the topic/fix-explorer-shutdown branch March 6, 2022 07:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants