DanielLeens commented on PR #11912: URL: https://github.com/apache/seatunnel/pull/11912#issuecomment-6646277945
Thanks @SEZ9. I checked the current source for F6: SchemaEvolutionSinkFlow.coordinate (common Flink schema package, lines 40-72) is the entry that selects the new coordinated applier/broadcast path; FlinkSink:103-113 checks the writer capability, and the Flink writer refresh path also checks it. A repository search found no Zeta or Spark consumer of SupportCoordinatedSchemaEvolutionSink on this head. Thus the new coordinated execution path is currently Flink-specific; that does not establish coordinated support on the other engines. Please state that scope in the SPI Javadoc as you suggested. The actual merge conflict remains a separate blocker: resolve it against dev while preserving the lazy applier creation, physical-table ambiguity rejection and these contracts, then push the resulting head for one complete re-review. The source findings already resolved on this head should not be reopened merely because a rebase is pending. This is an unchanged-head discussion reply, not another complete source review. Daniel has READ permission; technical approval and GitHub's effective maintainer gate are separate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
