VasShabu opened a new pull request, #28850:
URL: https://github.com/apache/flink/pull/28850
<!--
*Thank you very much for contributing to Apache Flink - we are happy that
you want to help us improve Flink. To help the community review your
contribution in the best possible way, please go through the checklist below,
which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a
hassle. In order to uphold a high standard of quality for code contributions,
while at the same time managing a large number of contributions, we need
contributors to prepare the contributions well, and give reviewers enough
contextual information for the review. Please also understand that
contributions that do not follow this guide will take longer to review and thus
typically be picked up with lower priority by the community.*
Jira-1728 is the internal ticket
- Make sure that the change passes the automated tests, i.e., `mvn clean
verify` passes. You can set up Azure Pipelines CI to do that following [this
guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
(including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
This PR is adding the implementation of the builting function JSON_TYPE
builtin function to Apache Flink.
*(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).)*
## Brief change log
*(for example:)*
- Added java codegen function
- Added function when after parsing will output the type of json
- Added docs (sql_functions.yml, sql_functions_zh.yml, BaseExpression.java,
expression.py) to document how/what the function works/does.
## Verifying this change
./mvnw -o -pl flink-table/flink-table-planner -Dtest='JsonFunctionsITCase'
-Dsurefire.failIfNoSpecifiedTests=false -Dcheckstyle.skip=true
-Dspotless.check.skip=true -e -Drat.skip=true -Denforcer.skip=true test
or (depending on version)
mvn -o -pl flink-table/flink-table-planner -Dtest='JsonFunctionsITCase'
-Dsurefire.failIfNoSpecifiedTests=false -Dcheckstyle.skip=true
-Dspotless.check.skip=true -e -Drat.skip=true -Denforcer.skip=true test
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).
This change added tests and can be verified as follows:
*(example:)*
- Added JSON_TYPE functionality
## 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: (don't know)
- The runtime per-record code paths (performance sensitive): (yes)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (don't know)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? (docs / JavaDocs ).
(sql_function.yml/expression.py)
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
<!--
Generated-by: Claude Opus 5
-->
--
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]
