You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/07/18 05:30:03 UTC

[GitHub] [flink] lincoln-lil commented on issue #9146: [FLINK-13284] [table-planner-blink] Correct some builtin functions' r…

lincoln-lil commented on issue #9146: [FLINK-13284] [table-planner-blink] Correct some builtin functions' r…
URL: https://github.com/apache/flink/pull/9146#issuecomment-512670571
 
 
   @godfreyhe @JingsongLi  Agree with you that we should offer a deterministic semantic for those 'dirty data', I think we can achieve this for two steps:
   1. unify all the builtin functions' exception handling behavior for blink planner(since it differs with flink planner), I found two exception functions and will create another issue to fix it.
   2. add a global configuration to support something like [MySQL's strict/non-strict sql mode](https://dev.mysql.com/doc/refman/5.6/en/sql-mode.html#sql-mode-strict) for exception handling includes numeric out-of-range and overflow and illegal inputs for sources. We can start a new thread to discuss it, 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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services