-
Notifications
You must be signed in to change notification settings - Fork 591
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): support different default sink decouple for different sink #12544
Conversation
Codecov Report
@@ Coverage Diff @@
## main #12544 +/- ##
==========================================
- Coverage 69.43% 69.42% -0.01%
==========================================
Files 1481 1482 +1
Lines 242791 242849 +58
==========================================
+ Hits 168573 168608 +35
- Misses 74218 74241 +23
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 2 files with indirect coverage changes 📣 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.
Left a question. Rest LGTM
"have checked connector is contained when create the `StreamSink`" | ||
).to_lowercase().as_str(), | ||
SinkTypeName, | ||
SinkTypeName::default_sink_decouple(), |
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.
Is the plan to change this to let different sink's implementation to specify whether sink decouple is enabled in the future?
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.
Yes. In the future different sinks will have different default sink decouple setting.
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, good work
#12544) (#12746) Co-authored-by: William Wen <[email protected]>
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
In this PR, we support specifying the default sink_decouple of each sink. Currently the default sink decouple of all sinks is
false
. In the originalsink_decouple
session variable, its default value becomesdefault
, which means that it will adopt the default sink decouple of the sink itself. The variable can be settrue
orenable
to enable sink decouple for all sinks created in the session orfalse
anddisable
to disable it regardless of the default sink decouple.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.