[jira] [Commented] (HIVE-2838) cleanup readentity/writeentity

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548093#comment-13548093 ] 

Hudson commented on HIVE-2838:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-2838. cleanup readentity/writeentity. (namit via kevinwilfong) (Revision 1298699)

     Result = ABORTED
kevinwilfong : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1298699
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/hooks/Entity.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/hooks/ReadEntity.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/hooks/WriteEntity.java

                
> 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: ASF.LICENSE.NOT.GRANTED--HIVE-2838.D2193.1.patch, ASF.LICENSE.NOT.GRANTED--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
For more information on JIRA, see: http://www.atlassian.com/software/jira