We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometimes in testing we also hope to test the recovery path beside the normal path.
For example, when creating a streaming job:
With a SQL (?) command to trigger recovery manually, we may cover this cases better.
No response
The text was updated successfully, but these errors were encountered:
Somehow related to #14438 (comment).
Sorry, something went wrong.
Not just in testing, but trigger recovery under high barrier latency to let alter rate limit / drop stream job take effect immediately.
RECOVER
kwannoel
Successfully merging a pull request may close this issue.
Is your feature request related to a problem? Please describe.
Sometimes in testing we also hope to test the recovery path beside the normal path.
For example, when creating a streaming job:
With a SQL (?) command to trigger recovery manually, we may cover this cases better.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: