[jira] [Comment Edited] (CALCITE-1975) make some method in SqlTypeFactoryImpl public

["Ruidong Li (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158033#comment-16158033 ] 

Ruidong Li edited comment on CALCITE-1975 at 9/8/17 2:31 AM:
-------------------------------------------------------------

Flink's ANY time has an inner field , when using Calcite's {{createSqlType(SqlTypeName.ANY)}}, it only returns a BasicSqlType which causing lose of , I think it's better to add one more parameter {{RelDataType}}  to {{createSqlType}}'s signature to {{createSqlType(SqlTypeName, RelDataType dataType)}} , so other system get enough info to handle it's own type.


was (Author: ruidongli):
Flink's ANY time has a field , when using Calcite's {{createSqlType(SqlTypeName.ANY)}}, it only returns a BasicSqlType which causing lose of , I think it's better to add one more parameter {{RelDataType}}  to {{createSqlType}}'s signature to {{createSqlType(SqlTypeName, RelDataType dataType)}} , so other system get enough info to handle it's own type.

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