[
https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131186#comment-13131186
]
John Sichi commented on HIVE-2509:
----------------------------------
1) So for the array case, you're going to stick an L on the end of every
literal in the array? An explicit CAST seems cleaner in that case (assuming it
works). What are some other cases? I'd like to understand them better before
we add more Hive-specific syntax (I'm not aware of any other SQL parsers that
use the L suffix).
2) In standard SQL, that would be an error since strings and numbers are not
union-compatible. Simple. I wish Hive followed standard SQL in this and many
other areas (such as comparison strictness).
> Literal bigint
> --------------
>
> Key: HIVE-2509
> URL: https://issues.apache.org/jira/browse/HIVE-2509
> Project: Hive
> Issue Type: New Feature
> Reporter: Jonathan Chang
> Assignee: Jonathan Chang
> Attachments: D15.1.patch, D15.1.patch
>
>
> Typing bigints is a pain because you have to write CAST(0 AS BIGINT). We
> should let people type 0L instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
