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

feat(sink): add blackhole sink #6756

Merged
merged 3 commits into from
Dec 7, 2022
Merged

feat(sink): add blackhole sink #6756

merged 3 commits into from
Dec 7, 2022

Conversation

lmatz
Copy link
Contributor

@lmatz lmatz commented Dec 6, 2022

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
  • I have added necessary unit tests and integration tests
  • All checks passed in ./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.

  • Connector (sources & sinks)
  • SQL commands, functions, and operators

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)

@lmatz lmatz added component/connector user-facing-changes Contains changes that are visible to users labels Dec 6, 2022
@codecov
Copy link

codecov bot commented Dec 6, 2022

Codecov Report

Merging #6756 (7efaa81) into main (7e3e7cb) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            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     
Flag Coverage Δ
rust 73.20% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
src/connector/src/sink/mod.rs 0.00% <0.00%> (ø)
src/stream/src/executor/aggregation/minput.rs 96.39% <0.00%> (-0.11%) ⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@lmatz lmatz requested a review from tabVersion December 7, 2022 03:28
Copy link
Contributor

@tabVersion tabVersion left a 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?

@mergify
Copy link
Contributor

mergify bot commented Dec 7, 2022

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 git commit --allow-empty -m "rerun" && git push.

@mergify mergify bot merged commit 8b46da1 into main Dec 7, 2022
@mergify mergify bot deleted the lz/blackhole branch December 7, 2022 07:05
@hengm3467
Copy link
Contributor

@lmatz I don't feel this sink should be documented. What do you think? Thanks.

@lmatz
Copy link
Contributor Author

lmatz commented Dec 20, 2022

@lmatz I don't feel this sink should be documented. What do you think? Thanks.

It's fine, not a must right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/connector type/feature user-facing-changes Contains changes that are visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants