gustavodemorais opened a new pull request, #28125: URL: https://github.com/apache/flink/pull/28125
## What is the purpose of the change CAST from BINARY/VARBINARY/BYTES to a CHAR/VARCHAR/STRING type now validates UTF-8 and throws on invalid input instead of silently substituting U+FFFD. A new ExecutionConfigOption restores the prior behaviour for users who need it. Part of FLIP-568. ## Brief change log - Add ExecutionConfigOptions.TABLE_EXEC_LEGACY_BYTES_TO_STRING_CAST (default false). - Update BinaryToStringCastRule with a strict UTF-8 fast path for unbounded targets and a strict decode in the round-trip path; override canFail. - Add BINARY_STRING_DATA_FROM_UTF8_BYTES to BuiltInMethods. - Update CAST and MAKE_VALID_UTF8 entries in sql_functions.yml and sql_functions_zh.yml. - Add a flink-2.4 release note for the breaking change. ## Verifying this change - CastRulesTest - CastFunctionMiscITCase ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: yes - new ConfigOption on ExecutionConfigOptions - The serializers: no - The runtime per-record code paths (performance sensitive): yes - per-record CAST(BYTES AS STRING) now validates UTF-8; the fast path wraps bytes with one validating walk - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? sql_functions.yml, sql_functions_zh.yml, execution_config_configuration.html, flink-2.4 release notes --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) 2.1.117 (Claude Code) -- 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]
