DanielLeens commented on issue #12714: URL: https://github.com/apache/seatunnel/issues/12714#issuecomment-6108866002
Classification: A / Transform-V2 MD5 deterministic value correctness. The report matches current dev: SeaTunnel represents `ARRAY<BYTE>` as `Byte[]`, while `StringFunction.md5` only recognizes primitive `byte[]` and otherwise hashes `toString()`. Rejecting arrays is a valid safe contract because it prevents a value derived from a JVM identity string; it must retain the existing primitive `byte[]` raw-binary behavior. #12717 is the only implementation to continue, but it is not independently scoped yet: its current diff also contains the unmerged WebSocket fix from #12716. Please rebase it to a current `dev` baseline after that work is separated, or otherwise remove the unrelated change. Add a SQL-path regression using an actual `ARRAY<BYTE>` column and `SELECT MD5(...)`, not only a direct `StringFunction` call, so the parser and executor path demonstrate the defined failure while the primitive-byte control remains unchanged. The PR Build is ACTION_REQUIRED and it still needs review, so this is not fixed in dev. -- 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]
