You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Phabricator (JIRA)" <ji...@apache.org> on 2012/05/02 03:14:53 UTC
[jira] [Commented] (HIVE-2838) cleanup readentity/writeentity
[ https://issues.apache.org/jira/browse/HIVE-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266277#comment-13266277 ]
Phabricator commented on HIVE-2838:
-----------------------------------
njain has abandoned the revision "HIVE-2838 [jira] cleanup readentity/writeentity".
REVISION DETAIL
https://reviews.facebook.net/D2193
> 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