DanielLeens commented on issue #10889: URL: https://github.com/apache/seatunnel/issues/10889#issuecomment-4597811050
I still think this should stay as an umbrella/design issue rather than turning into several implementation tracks in parallel too early. The direction is valuable, but the most important thing right now is to keep a single design checkpoint in front of the follow-up PR train. In practice, that means PR-A / Gate 0 should still be the next artifact to stabilize before we widen execution. That first checkpoint should lock down at least these boundaries: 1. the semantic metadata contract for document/chunk identity and change detection 2. the Zeta-first MVP scope versus what is explicitly out of scope 3. the engine contract for routing / non-Zeta fail-fast behavior 4. the first end-to-end chain we want the community to review before more sub-features branch off Once that foundation is written down, it becomes much safer to split ownership across metadata contract, dedicated sources, lifecycle sinks, and later multimodal work. So I would suggest continuing to use this issue as the umbrella tracker, but keeping the next concrete review target narrow: Gate 0 first, then the sub-issues/PR slices behind it. -- 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]
