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

Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2019/12/19 16:49:00 UTC

[jira] [Closed] (FLINK-15149) Merge InputTypeStrategy and InputTypeValidator

     [ https://issues.apache.org/jira/browse/FLINK-15149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther closed FLINK-15149.
--------------------------------
    Fix Version/s: 1.10.0
       Resolution: Fixed

Fixed in 1.11: e72a5a7ea41b307a0b6393d1988a5ebf90720e23
Fixed in 1.10: 72d2734a79dbcddb97397cee695f4439944c1db2

> Merge InputTypeStrategy and InputTypeValidator
> ----------------------------------------------
>
>                 Key: FLINK-15149
>                 URL: https://issues.apache.org/jira/browse/FLINK-15149
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Due to the design of Calcite, even operand checkers that were originally used for "checking" can infer and modify call arguments nowadays. This conflicts with our original design of separating validation and input type inference. Therefore, we propose to merge those two concepts in Flink into one `InputTypeStrategy` that is responsible for both inferring/enriching and validation.



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