hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-2838) cleanup readentity/writeentity
Date Thu, 08 Mar 2012 21:15:59 GMT

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

Phabricator updated HIVE-2838:
------------------------------

    Attachment: HIVE-2838.D2193.2.patch

njain updated the revision "HIVE-2838 [jira] cleanup readentity/writeentity".
Reviewers: JIRA, kevinwilfong

  Comments

REVISION DETAIL
  https://reviews.facebook.net/D2193

AFFECTED FILES
  ql/src/java/org/apache/hadoop/hive/ql/hooks/WriteEntity.java
  ql/src/java/org/apache/hadoop/hive/ql/hooks/ReadEntity.java
  ql/src/java/org/apache/hadoop/hive/ql/hooks/Entity.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
>         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

        

Mime
View raw message