-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove unbounded_input from FileSinkOptions #8605
Remove unbounded_input from FileSinkOptions #8605
Conversation
68eed86
to
740d427
Compare
datafusion/proto/gen/src/main.rs
Outdated
@@ -28,6 +28,7 @@ fn main() -> Result<(), String> { | |||
let descriptor_path = proto_dir.join("proto_descriptor.bin"); | |||
|
|||
prost_build::Config::new() | |||
.protoc_arg("--experimental_allow_proto3_optional") |
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.
Should be able to remove this after #8602 is fixed
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.
Removed merged main, and confirmed that 8602 is fixed for me as well
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.
Thank you (again) @devinjdangelo
@metesynnada / @ozankabak can you please also review this PR to make sure we are not removing something that is important for your usecase?
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.
🚀 |
Which issue does this PR close?
None, but related to #8604
Rationale for this change
Now that writing unbounded (streaming) sources is supported via
StreamWrite
, otherDataSink
impls do not need to worry about yielding on unbounded input plans.What changes are included in this PR?
Removes unbounded_input checks in FileSinkConfig
Are these changes tested?
Yes, by existing tests
Are there any user-facing changes?
No