[
https://issues.apache.org/jira/browse/HIVE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535453#comment-13535453
]
Gunther Hagleitner commented on HIVE-2693:
------------------------------------------
Ordering: The stripTrailingZeros() does not change the value of the BigDecimal
and therefore doesn't change the serialized output. I don't think this is the
culprit. The order of the output depends on what hadoop does in the
shuffle/sort phase. My guess is that since you changed the input the results
that mapred came up with where different. Hadoop doesn't guarantee stable sort
afaik.
Where clause: Yes, it's one and the same problem. We end up comparing 3.14 with
3.140000...1243... Still debugging but it seems we're going through double on
the way to BigDecimal which changes the number.
> Add DECIMAL data type
> ---------------------
>
> Key: HIVE-2693
> URL: https://issues.apache.org/jira/browse/HIVE-2693
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor, Types
> Affects Versions: 0.10.0
> Reporter: Carl Steinbach
> Assignee: Prasad Mujumdar
> Attachments: 2693_7.patch, 2693_8.patch, 2693_fix_all_tests1.patch,
> HIVE-2693-10.patch, HIVE-2693-11.patch, HIVE-2693-12-SortableSerDe.patch,
> HIVE-2693-13.patch, HIVE-2693-1.patch.txt, HIVE-2693-all.patch,
> HIVE-2693-fix.patch, HIVE-2693.patch, HIVE-2693-take3.patch,
> HIVE-2693-take4.patch
>
>
> Add support for the DECIMAL data type. HIVE-2272 (TIMESTAMP) provides a nice
> template for how to do this.
--
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
