hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-3190) allow INTEGER as a type name in a column/cast expression (per ISO-SQL 2011)
Date Wed, 30 Oct 2013 18:53:26 GMT

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

Jason Dere updated HIVE-3190:
-----------------------------

    Attachment: HIVE-3190.2.patch

Tried doing Xuefu's suggestion of doing some of the aliases as lexer rules. Could not do this
with BINARY/BLOB because this would have resulted BLOB LARGE OBJECT being legal.  Which is
the danger of doing it in the lexer - I think i general it's probably better to have each
keyword parsed as its on token.

> 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, HIVE-3190.2.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)

Mime
View raw message