SEZ9 commented on issue #11857: URL: https://github.com/apache/seatunnel/issues/11857#issuecomment-5806575572
Thanks for taking this on, @nzw921rx, and for writing up the proposed layout. A quick note on the structure: placing `resource-managers/` at the repository root next to `seatunnel-engine` is a reasonable direction, but for now it should be treated as a proposal rather than a settled module boundary. The class inventory is a good starting point, but the names alone do not tell us who owns which lifecycle, and that is the part to pin down before code. Since you suggested YARN should be the priority, a YARN-first STIP linked here would be the best next step before opening modules, touching POMs, or pulling in platform SDKs. Once the contract is agreed we can split out implementation issues. <!-- streview-comment:1275 --> -- 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]
