VasShabu opened a new pull request, #28815:
URL: https://github.com/apache/flink/pull/28815
## What is the purpose of the change
*(For example: This pull request makes task deployment go through the blob
server, rather than through RPC. That way we avoid re-transferring them on each
deployment (during recovery).)*
This change changing the setting of the Jackson Parser to ensure that the
parser fails on trailing tokens, In doing this some invalid JSON in the
JSON_UNQUOTE function caused errors.
## Brief change log
*(for example:)*
- Ensured that failing on leading token got enabled
- Corrected the invalid JSON that was present in the JSON_UNQUOTE function
## Verifying this change
Please make sure both new and modified tests in this PR follow [the
conventions for tests defined in our code quality
guide](https://flink.apache.org/how-to-contribute/code-style-and-quality-common/#7-testing).
*(Please pick either of the following options)*
This change added tests and can be verified as follows:
Some tests were added as this PR
- SELECT 'true, false' IS JSON; // False
- SELECT 'true sdfoishjdoifhfs' IS JSON; // False
Previously these functions returned true
## 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)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): (yes)
- 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? (no)
- If yes, how is the feature documented? (not applicable)
<!--
Generated-by: Claude Opus 4.8
-->
--
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]
