[
https://issues.apache.org/jira/browse/CALCITE-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159657#comment-16159657
]
Ruidong Li edited comment on CALCITE-1975 at 9/9/17 1:52 AM:
-------------------------------------------------------------
FLink's has only one ANY type as below:
{code}
class GenericRelDataType(
val typeInfo: TypeInformation[_],
val nullable: Boolean,
typeSystem: RelDataTypeSystem)
extends BasicSqlType(
typeSystem,
SqlTypeName.ANY) {
}
{code}
if two table A and B with {GenericRelDataType} are dealing with Set Operation
like Union
`A (Int, GenericRelDataType) union B(Int,GenericRelDataType )`
the result will be `C (Int, BasicSqlType(ANY))` which it loses `typeInfo` and
can't get it back, this is why I want Calcite's ANY type to be extended
was (Author: ruidongli):
FLink's has only one ANY type as below:
{code}
class GenericRelDataType(
val typeInfo: TypeInformation[_],
val nullable: Boolean,
typeSystem: RelDataTypeSystem)
extends BasicSqlType(
typeSystem,
SqlTypeName.ANY) {
}
{code}
if two table A and B with {GenericRelDataType}s in and are handling Set
Operation like Union
A (Int, GenericRelDataType) union B(Int,GenericRelDataType )
the result will be C (Int, BasicSqlType(ANY)) which it lose `typeInfo` and
can't get it back, this is why I want Calcite's ANY type to be extended
> make some method in SqlTypeFactoryImpl public
> ---------------------------------------------
>
> Key: CALCITE-1975
> URL: https://issues.apache.org/jira/browse/CALCITE-1975
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Ruidong Li
> Assignee: Julian Hyde
>
> Some other project which use calcite may have it's own logic in
> {{leastRestrictiveByCast}} and {{leastRestrictiveSqlType}}. For example,
> Flink's {{ANY}} SqlType differs from calcite's , it'e better to implementing
> it's own logic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
