-
Notifications
You must be signed in to change notification settings - Fork 21
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
Refactor FileSinkBuilder #785
Conversation
…equired File sinks were not made anywhere without providing a file_upload. A file_upload must be provided to construct a sink. Removes the old idea of a deposit that was dormant in the code. Removes needing to manage to potentially two sinks that were mutually exclusive in implementation.
b657491
to
e8638aa
Compare
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.
One thing to consider here, some non oracle applications may be using the old deposits. I guess things will break should they update to latest filestore and force a refactor
Great point, here's something for the release notes.
|
FileSink.file_upload
was added as an alternativeFileSink.deposits
.They behave in a mutually exclusive manner, and no production code was constructing a
FileSink
without providing aFileUpload
. (There was one test that made a FileSink without a destination channel).This PR removes the ability to use
FileSinkBuilder.deposits
and the correspondingFileSink.deposits
;and requires a
FileUpload
when constructing aFileSinkBuilder
.