[
https://issues.apache.org/jira/browse/HIVE-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000157#comment-14000157
]
Sushanth Sowmyan commented on HIVE-7067:
----------------------------------------
I'm okay with backporting this to 0.13.1, but I want to follow the process I
set out for candidates for late inclusion for 0.13.1, and for that, I need two
+1s for this. [~thejas] / [~hagleitn] / [~jdere] , would you please confirm
that you're okay with this inclusion request?
> Min() and Max() on Timestamp and Date columns for ORC returns wrong results
> ---------------------------------------------------------------------------
>
> Key: HIVE-7067
> URL: https://issues.apache.org/jira/browse/HIVE-7067
> Project: Hive
> Issue Type: Bug
> Reporter: Prasanth J
> Assignee: Prasanth J
> Priority: Critical
> Fix For: 0.14.0
>
> Attachments: HIVE-7067.1.patch, HIVE-7067.2.patch,
> HIVE-7067.branch-13.2.patch
>
>
> min() and max() of timestamp and date columns of ORC table returns wrong
> results. The reason for that is when ORC creates object inspectors for date
> and timestamp it uses JAVA primitive objects as opposed to WRITABLE objects.
> When get() is performed on java primitive objects, a reference to the
> underlying object is returned whereas when get() is performed on writable
> objects, a copy of the underlying object is returned.
> Fix is to change the object inspector creation to return writable objects for
> timestamp and date.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
