Re: [DISCUSS] FLIP-264 Extract BaseCoordinatorContext

y >> need >> > to >> > > refactor the SourceCoordinatorContext? You could simply add your own >> > > coordinator code. I'm not sure the sink requirements map to the source >> > > interface so closely that you can reuse the same logic. >> >

Re: [DISCUSS] FLIP-264 Extract BaseCoordinatorContext

d reason, normal operators should not support the > coordinator functionality. At least I'm not convinced it would play well > with Flink's execution model. But I see how it is required for sources and > sinks. > > -Max > > On Wed, Oct 26, 2022 at 3:05 PM gang ye wrote

Re: [DISCUSS] FLIP-264 Extract BaseCoordinatorContext

>> > > someone else could shed some light on this? >> >> > > >> >> > > Conceptually I would be actually in favour of exposing operator >> >> > > coordinators if there is a good reason behind that, but it is a &

[DISCUSS] FLIP-264 Extract BaseCoordinatorContext

Hi, We submit the Flip proposal at Confluent to extract BaseCoordinatorContext from SourceCoordinatorContext to reuse it for other coordinators E.g. in the shuffling support of Flink Iceberg sink

[jira] [Created] (FLINK-27405) Refactor SourceCoordinator to abstract BaseCoordinator implementation

gang ye created FLINK-27405: --- Summary: Refactor SourceCoordinator to abstract BaseCoordinator implementation Key: FLINK-27405 URL: https://issues.apache.org/jira/browse/FLINK-27405 Project: Flink