matriv commented on pull request #18221: URL: https://github.com/apache/flink/pull/18221#issuecomment-1009810797
For me what we have now in master, is a UTF8 representation of the bytes, which I see as a sub case and not the common usage. Hex representation to me makes more sense for the CAST, and then if we want string representation we should definitely introduce dedicate function(s) with args where the user can also defined the charset, as also static UTF8 won't work for every use case. So, to conclude, I'd go with the Hex representation for CAST (back and forth) and use the `legacyBehaviour` flag to keep the UTF8 (`escape`) behaviour we had before. @twalthr also agrees with that. @wuchong what do you think? -- 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]
