DanielLeens commented on issue #12814: URL: https://github.com/apache/seatunnel/issues/12814#issuecomment-6233673712
Thank you — this is now a sufficiently precise implementation contract. The guard must run before `MultiTableManager.mergeSchema`, apply the carrier only when every participating container is `ROW`, and reject arrays/maps or malformed carrier text without silently changing their meaning. Keeping the source-side MySQL wide-DECIMAL mapping separately in #12841 is also the right boundary. Please implement this as a focused PR with the stated Spark 2.4 and 3.3 coverage for top-level and nested ROW cases, mixed schemas, malformed carrier text, nulls, and decimal scale preservation. Classification: D — Spark schema-conversion design. -- 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]
