[
https://issues.apache.org/jira/browse/HIVE-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799399#comment-13799399
]
Jason Dere commented on HIVE-3976:
----------------------------------
Actually my comment was supposed to be about HIVE-5564 - would doing what I
described allow legacy decimals to work without without the error? Since
"decimal" should only ever show up as a typeinfo string for legacy decimal
columns, you could even register decimalTypeInfo (currently decimal(65,30) in
your patch) as the typeinfo for "decimal". This would give backward-compatible
behavior for legacy decimal columns, and sql-compliant behavior for new decimal
columns due to the behavior you describe in your previous comment.
> Support specifying scale and precision with Hive decimal type
> -------------------------------------------------------------
>
> Key: HIVE-3976
> URL: https://issues.apache.org/jira/browse/HIVE-3976
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor, Types
> Affects Versions: 0.11.0
> Reporter: Mark Grover
> Assignee: Xuefu Zhang
> Fix For: 0.13.0
>
> Attachments: HIVE-3976.1.patch, HIVE-3976.2.patch, HIVE-3976.3.patch,
> HIVE-3976.4.patch, HIVE-3976.5.patch, HIVE-3976.6.patch, HIVE-3976.7.patch,
> HIVE-3976.8.patch, HIVE-3976.9.patch, HIVE-3976.patch, remove_prec_scale.diff
>
>
> HIVE-2693 introduced support for Decimal datatype in Hive. However, the
> current implementation has unlimited precision and provides no way to specify
> precision and scale when creating the table.
> For example, MySQL allows users to specify scale and precision of the decimal
> datatype when creating the table:
> {code}
> CREATE TABLE numbers (a DECIMAL(20,2));
> {code}
> Hive should support something similar too.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
