[
https://issues.apache.org/jira/browse/CALCITE-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913859#comment-16913859
]
feng huang commented on CALCITE-3282:
-------------------------------------
[~danny0405] Of course, it's not an easy work. currently, the unparse logic is
in SqlTypeNameSpec where SqlDialect can't modify. Maybe we can add
unparseDataType method in SqlDialect which just invoke the unparse logic is in
SqlTypeNameSpec , and then users can extend Specific SqlDialect such
HiveSqlDialect to implement their own unparse dataType logic.
> Make every SqlDialect unparse their own data type
> -------------------------------------------------
>
> Key: CALCITE-3282
> URL: https://issues.apache.org/jira/browse/CALCITE-3282
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: feng huang
> Priority: Minor
>
> Every database might have different type or same type but different type
> name, therefore making every SqlDialect parse their own data type is a
> suitable way.
> for example, “select cast(col as int) from table” change to hive sql "select
> cast(col as integer) from table", but "integer" is not allowed in hive.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
