[
https://issues.apache.org/jira/browse/HIVE-5565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-5565:
------------------------------
Description:
With HIVE-3976, the maximum precision is set to 65, and maximum scale is to 30.
After discussing with several folks in the community, it's determined that 38
as a maximum for both precision and scale are probably sufficient, in addition
to the potential performance boost that might become possible to some
implementation.
This task is to make such a change. The change is expected to be trivial, but
it may impact many test cases. The reason for a separate JIRA is that patch in
HIVE-3976 is already in a good shape. Rather than destabilizing a bigger patch,
a dedicate patch will facilitates both reviews.
The wiki document will be updated shortly.
was:
With HIVE-3976, the maximum precision is set to 65, and maximum scale is to 30.
After discussing with several folks in the community, it's determined that 38
as a maximum for both precision and scale are probably sufficient, in addition
to the potential performance boost that might become possible to some
implementation.
This task is to make such a change. The change is expected to be trivial, but
it may impact many test cases. The reason for a separate JIRA is that patch in
HIVE-3976 is already in a good shape. Rather than destabilizing a bigger patch,
a dedicate patch will facilitates both reviews.
> Limit Hive decimal type maximum precision and scale to 38
> ---------------------------------------------------------
>
> Key: HIVE-5565
> URL: https://issues.apache.org/jira/browse/HIVE-5565
> Project: Hive
> Issue Type: Task
> Components: Types
> Affects Versions: 0.13.0
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
> Fix For: 0.13.0
>
>
> With HIVE-3976, the maximum precision is set to 65, and maximum scale is to
> 30. After discussing with several folks in the community, it's determined
> that 38 as a maximum for both precision and scale are probably sufficient, in
> addition to the potential performance boost that might become possible to
> some implementation.
> This task is to make such a change. The change is expected to be trivial, but
> it may impact many test cases. The reason for a separate JIRA is that patch
> in HIVE-3976 is already in a good shape. Rather than destabilizing a bigger
> patch, a dedicate patch will facilitates both reviews.
> The wiki document will be updated shortly.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
