[
https://issues.apache.org/jira/browse/HIVE-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809133#comment-13809133
]
Xuefu Zhang commented on HIVE-3190:
-----------------------------------
[~jdere] It might be simpler if we treat those as syntactic flavours. Thus, you
might be able to have something like this:
{code|
KW_INT : INT
| INTEGER
;
{code}
Then, you don't need anything after that.
> allow INTEGER as a type name in a column/cast expression (per ISO-SQL 2011)
> ---------------------------------------------------------------------------
>
> Key: HIVE-3190
> URL: https://issues.apache.org/jira/browse/HIVE-3190
> Project: Hive
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 0.8.0
> Reporter: N Campbell
> Attachments: HIVE-3190.1.patch
>
>
> Just extend the parser to allow INTEGER instead of making folks use INT
> select cast('10' as integer) from cert.tversion tversion
> FAILED: Parse Error: line 1:20 cannot recognize input near 'integer' ')'
> 'from' in primitive type specification
--
This message was sent by Atlassian JIRA
(v6.1#6144)
