fhueske opened a new pull request, #28741:
URL: https://github.com/apache/flink/pull/28741

   ## What is the purpose of the change
   
   This PR fixes the nullability of the `IS JSON` functions.
   Calcite pre-1.38.0 had defined the return types of these functions as 
non-nullable booleans which was not standard compliant. Flink followed Calcite 
on this.
   With Calcite 1.38.0 this was fixed on Calcite's side but Flink maintained 
the old behavior.
   
   This PR fixes the nullability of the IS JSON functions.
   This is a breaking change that was discussed on the Flink mailing list. 
   The fix will be release with Flink 2.4.
   
   ## Brief change log
   
   * delete `StdSqlOperatorTable` which was copied and patched from Calcite to 
maintain the old behavior.
   * fix the code generation to produce `NULL` for `NULL` input
   * update the examples in the function documentation
   
   ## Verifying this change
   
   * existing tests that were extended with more `NULL` input cases
   
   ## 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? docs have been adjusted
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code 2.1.200 (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]

Reply via email to