SEZ9 commented on PR #11307: URL: https://github.com/apache/seatunnel/pull/11307#issuecomment-6553372172
Thanks for the update at 5184b37259aa. From the thread I can see the Unix launcher now passes raw NUL-delimited arguments as a quoted argv array (F2/F6), `SparkRowEncoder` resolves `Encoders.row` at runtime with a fallback and `useCommitCoordinator` is explicit (F3), and a scheduled Spark 3.5 connector container is registered. I'll verify those against the diff rather than ask you to restate them. A few points I can't yet trace from the thread: 1. **F1 / F5** – How does the Windows launcher now handle `!errorlevel!`/`!CMD!` expansion relative to `setlocal`, and how is a non-zero exit code propagated when the starter java process fails with no stdout? 2. **F4** – Which single SLF4J provider ends up under `starter/logging/*` for the Spark 3.5 starter? 3. **F7** – Does the scheduled Spark 3.5 container exercise the micro-batch streaming path that the quick-start docs point Spark 3.5 users at? If not, softening that wording would be fine. 4. **F8** – What guidance do Spark 3.4.x users now get in the engine docs? Pointers to the relevant files in the diff are enough; I'll confirm from there. <!-- streview-comment:2199 --> -- 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]
