[
https://issues.apache.org/jira/browse/HIVE-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634099#comment-13634099
]
Hudson commented on HIVE-4320:
------------------------------
Integrated in Hive-trunk-h0.21 #2068 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/2068/])
HIVE-4320 : Consider extending max limit for precision to 38 (Gunther
Hagleitner via Ashutosh Chauhan) (Revision 1468588)
Result = FAILURE
hashutosh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1468588
Files :
*
/hive/trunk/common/src/java/org/apache/hadoop/hive/common/type/HiveDecimal.java
* /hive/trunk/data/files/kv8.txt
* /hive/trunk/ql/src/test/results/clientpositive/decimal_precision.q.out
* /hive/trunk/ql/src/test/results/clientpositive/decimal_udf.q.out
> Consider extending max limit for precision to 38
> ------------------------------------------------
>
> Key: HIVE-4320
> URL: https://issues.apache.org/jira/browse/HIVE-4320
> Project: Hive
> Issue Type: Bug
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Fix For: 0.11.0
>
> Attachments: HIVE-4320.1.patch, HIVE-4320.2.patch
>
>
> Max precision of 38 still fits in 128. It changes the way you do math on
> these numbers though. Need to see if there will be perf implications, but
> there's a strong case to support 38 (instead of 36) to comply with other DBs.
> (Oracle, SQL Server, Teradata).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
