[
https://issues.apache.org/jira/browse/HIVE-8745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200678#comment-14200678
]
Gunther Hagleitner commented on HIVE-8745:
------------------------------------------
[~xuefuz] I'm going to revert HIVE-7373. I think that's reasonable given that
it causes this issues. I'm also worried to change the behavior of decimals in
hive .14 again if there's still questions about it. We've changed the behavior
in .12 - .13 already and it caused a lot of grief to some folks. Given that
BinarySortableSerde is involved, we also need to look into window functions,
group by w/ w/o map-side aggr etc.
Jason also brings up another good point: Performance. The decision to maintain
the trailing zeroes for each individual value instead of at the column level,
means that we will never be able to simply encode decimals in two longs, which
was the idea behind limiting the precision of decimals in the first place.
> Joins on decimal keys return different results whether they are run as reduce
> join or map join
> ----------------------------------------------------------------------------------------------
>
> Key: HIVE-8745
> URL: https://issues.apache.org/jira/browse/HIVE-8745
> Project: Hive
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Gunther Hagleitner
> Assignee: Jason Dere
> Priority: Critical
> Fix For: 0.14.0
>
> Attachments: join_test.q
>
>
> See attached .q file to reproduce. The difference seems to be whether
> trailing 0s are considered the same value or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
