Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 30 Oct 2013 19:07:28 +0000 (UTC)
From: "Jason Dere (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12595720.1340551511790.6944.1383160048283@arcas>
In-Reply-To: <JIRA.12595720.1340551511790@arcas>
References: <JIRA.12595720.1340551511790@arcas>
Subject: [jira] [Commented] (HIVE-3190) allow INTEGER as a type name in a
 column/cast expression (per ISO-SQL 2011)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Dere commented on HIVE-3190:
----------------------------------

The issue would have been if we had put the folliowing alias rule in the lexer:
{noformat}
KW_BINARY: 'BINARY' | 'BLOB'
{noformat}
which would have been bad because the parsing rules would then allow BLOB LARGE OBJECT, in addition to BINARY LARGE OBJECT. So BINARY and BLOB need to stay as separate keywords in the lexer rules.

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