Skip to content

Conversation

@Forkast
Copy link

@Forkast Forkast commented Sep 18, 2023

It looks like FanoutWriter is not public by mistake. Right now the only way to implement FanoutWriter is to implement FanoutDataWriter which is not ideal. The analogous class PartitionedFanoutWriter was made public in this PR: #1774

@github-actions github-actions bot added the core label Sep 18, 2023
* this writer only when clustering by spec/partition is not possible (e.g. streaming).
*/
abstract class FanoutWriter<T, R> implements PartitioningWriter<T, R> {
public abstract class FanoutWriter<T, R> implements PartitioningWriter<T, R> {
Copy link
Contributor

@aokolnychyi aokolnychyi Sep 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was actually done on purpose as it is a parent class. We expose FanoutDataWriter and related implementations. The same is also true for ClusteredWriter. Is there a particular need to expose this class? Is it something generic enough to live in the repo itself?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only difference between FanoutWriter and FanoutDataWriter is that the latter enforces the use of RollingDataWriter and adds quite a bit of complexity. I'd argue that both are equally useful and FanoutWriter is much easier to implement and does not enforce things like file name format for example.

@github-actions
Copy link

This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@iceberg.apache.org list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 20, 2024
@github-actions
Copy link

This pull request has been closed due to lack of activity. This is not a judgement on the merit of the PR in any way. It is just a way of keeping the PR queue manageable. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants