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

Posted to dev@flink.apache.org by "Terry Wang (Jira)" <ji...@apache.org> on 2020/04/20 08:49:00 UTC

[jira] [Created] (FLINK-17263) Remove RepeatFamilyOperandTypeChecker in blink planner and replace it with calcite's CompositeOperandTypeChecker

Terry Wang created FLINK-17263:
----------------------------------

             Summary: Remove RepeatFamilyOperandTypeChecker in blink planner and replace it  with calcite's CompositeOperandTypeChecker
                 Key: FLINK-17263
                 URL: https://issues.apache.org/jira/browse/FLINK-17263
             Project: Flink
          Issue Type: Improvement
          Components: Table SQL / Planner
    Affects Versions: 1.11.0
            Reporter: Terry Wang


Remove RepeatFamilyOperandTypeChecker in blink planner and replace it  with calcite's CompositeOperandTypeChecker.
It seems that what CompositeOperandTypeChecker can do is a super set of RepeatFamilyOperandTypeChecker. To keep code easy to read, it's better to do such refactor.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)