Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 15 May 2014 00:50:20 +0000 (UTC)
From: "Prasanth J (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12714373.1400114857641.356820.1400115020086@arcas>
In-Reply-To: <JIRA.12714373.1400114857641@arcas>
References: <JIRA.12714373.1400114857641@arcas>
Subject: [jira] [Updated] (HIVE-7067) Min() and Max() on Timestamp and Date
 columns for ORC returns wrong results
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanth J updated HIVE-7067:
-----------------------------

    Attachment: HIVE-7067.1.patch

> 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
>         Attachments: HIVE-7067.1.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)