-
Notifications
You must be signed in to change notification settings - Fork 599
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
feat(sink): add blackhole sink #6756
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6756 +/- ##
==========================================
- Coverage 73.20% 73.20% -0.01%
==========================================
Files 1024 1024
Lines 163733 163741 +8
==========================================
- Hits 119860 119859 -1
- Misses 43873 43882 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
LGTM
is it a feature for production?
Hey @lmatz, this pull request failed to merge and has been dequeued from the merge train. If you believe your PR failed in the merge train because of a flaky test, requeue it by clicking "Update branch" or pushing an empty commit with |
@lmatz I don't feel this sink should be documented. What do you think? Thanks. |
It's fine, not a must right now. |
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Blackhole sink does nothing, purely for performance test purposes.
So that branch https://github.com/risingwavelabs/risingwave/tree/disable_mv can be deleted.
Partially(?) unlock #5678, and performance test for stateless ETL cases.
Checklist
I have written necessary rustdoc comments./risedev check
(or alias,./risedev c
)Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
Please keep the types that apply to your changes, and remove those that do not apply.
Release note
Please create a release note for your changes. In the release note, focus on the impact on users, and mention the environment or conditions where the impact may occur.
Users can now create a sink with
blackhole
being the connector. It does nothing. It is helpful when we want to create a streaming query without a materialized view or a sink whose writes may affect the end-to-end performance.Refer to a related PR or issue link (optional)