You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Terry Wang (Jira)" <ji...@apache.org> on 2020/04/20 10:25:00 UTC
[jira] [Commented] (FLINK-17263) Remove
RepeatFamilyOperandTypeChecker in blink planner and replace it with
calcite's CompositeOperandTypeChecker
[ https://issues.apache.org/jira/browse/FLINK-17263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087585#comment-17087585 ]
Terry Wang commented on FLINK-17263:
------------------------------------
I open a [PR|https://github.com/apache/flink/pull/11819], and feel free assign this issue to me cc [~ykt836]
> 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
> Priority: Major
> Labels: pull-request-available
>
> 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)