-
Notifications
You must be signed in to change notification settings - Fork 590
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 json encode for file sink #18744
Conversation
assert_eq!(op, Op::Insert, "expect all `op(s)` to be `Op::Insert`"); | ||
// to prevent temporary string allocation, | ||
// so we directly write to `chunk_buf` implicitly via `write_fmt`. | ||
writeln!( |
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.
in snowflake sink, there are no line breaks between lines, but the file sink has.(I think it's more friendly with user).
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.
Has it been tested to import snowflake?
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.
No, I plan to deprecate snowflake sink in next pr, this pr only focus on file sink.
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
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
The implementation detail is almost the same with snowflake sink, and the difference is
uuid
to distinguish the parallelism, while the file sink directly usesexecutor_id
.Todo:
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
Add json encode for file sink, which allow user to sink json files into object storage.
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.