DanielLeens commented on issue #9764: URL: https://github.com/apache/seatunnel/issues/9764#issuecomment-5053232546
Yes — aligning this with the dry-run layering instead of creating a completely separate debug execution path makes sense to me. The local-only first scope also looks reasonable: - `--dry-run sample` with a small default row limit - real source + transform execution for preview - sink replacement with an internal preview sink so target-side writes never happen - no checkpoint restore, savepoint, or async behavior in this mode I also agree with your sink-side boundary: for v1 we should not call normal sink mutation paths just to preview DDL. A separate preview-oriented SPI, or an explicit `SKIPPED` result for unsupported sinks, is safer than accidentally touching external systems. So from my side, this is a good direction to continue refining. If you want to take the next step, a short class-level design and test plan in this thread, or a draft PR for the local-only first slice, would be a good way to move it forward. -- 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]
