Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 9 Mar 2012 04:20:02 +0000 (UTC)
From: "Kevin Wilfong (Updated) (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <98753496.42203.1331266802221.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2000463054.19958.1330881719956.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HIVE-2838) cleanup readentity/writeentity
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kevin Wilfong updated HIVE-2838:
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.9.0
           Status: Resolved  (was: Patch Available)

Committed, thanks Namit.
                
> cleanup readentity/writeentity
> ------------------------------
>
>                 Key: HIVE-2838
>                 URL: https://issues.apache.org/jira/browse/HIVE-2838
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>             Fix For: 0.9.0
>
>         Attachments: HIVE-2838.D2193.1.patch, HIVE-2838.D2193.2.patch
>
>
> Ideally, there should be one common entity instead of readentity/writeentity.
> Unfortunately, that would be a backward incompatible change since users os hive might have written
> there own hooks, where they are using readentity/writeentity.
> We should atleast create a common class, and then we can deprecate read/write entity later, for a new release.
> For now, I propose to make a backward compatible change.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira