SEZ9 commented on issue #12620: URL: https://github.com/apache/seatunnel/issues/12620#issuecomment-5988331613
Thanks for the enumerated baseline and for the correction on FieldRenameTransform/TableRenameTransform — good catch that both already use `Locale.ROOT` since #11994, so the "preserve intentional user-data casing" category currently has no members in this module. Agreed that this should wait until #12495 and #12618 land so the guard is evaluated against the post-fix baseline. Once they merge, it would be helpful to re-run the scan against the new `dev` HEAD and confirm the count is zero. On the three scope questions: given #11994 chose `Locale.ROOT` even for user-requested rename output and no surviving carve-out example exists, I'd lean toward a simple "always a fixed locale" rule with #11994 as the stated precedent, unless someone can point to a concrete user-visible case that needs the caller locale. Happy to hear other views on questions 2 and 3 before any mechanism is discussed. <!-- streview-comment:1533 --> -- 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]
