[
https://issues.apache.org/jira/browse/HIVE-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132099#comment-13132099
]
John Sichi commented on HIVE-2509:
----------------------------------
Based on what you're saying, it sounds like literal bigint is just a bandaid
for the real issues with collection types and casting. If you think the
non-portability is worth it, let's commit it, but in that case, shouldn't
syntactic shorthand be provided for the other integer types (TINYINT and
SMALLINT) as well for comprehensiveness?
Regarding proposed repairs to the type system, I'm all in favor of strong
typing combined with conservative comparison/widening/assignment rules plus
robust explicit conversions. However, getting from the existing liberal system
to the promised land may be difficult due to breakage in legacy queries.
> 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
