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

Timo Walther updated FLINK-14983:
---------------------------------
    Description: 
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.

  was:
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.


> 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
>
> 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)

Reply via email to