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/06 14:02:00 UTC

[jira] [Closed] (FLINK-14983) Add interfaces for input type inference

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

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

Fixed in 1.10.0: 06bfd9b2e37a3cb58573f485968217f6802869ff

> Add interfaces for input type inference
> ---------------------------------------
>
>                 Key: FLINK-14983
>                 URL: https://issues.apache.org/jira/browse/FLINK-14983
>             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: 20m
>  Remaining Estimate: 0h
>
> The [design document|https://docs.google.com/document/d/1RM_-XvD25AldUOl7xRSvA3sascWBa1-Jze3i5mvb7WU/edit#] around {{TypeInference}} already mentioned an {{InputTypesInference}} that enables the derivation of missing or incomplete input signatures. The Calcite equivalent is called {{SqlOperandTypeInference}}.
> For FLIP-65, we will need to implement those interfaces as the planner needs infer the {{DataType}} s out of logical types that come from the logical query. This is also beneficial to support the {{NULL}} literal in the future.



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