Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 22 Aug 2013 17:29:53 +0000 (UTC)
From: "Ashutosh Chauhan (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12641872.1365615833562.17871.1377192593426@arcas>
In-Reply-To: <JIRA.12641872.1365615833562@arcas>
References: <JIRA.12641872.1365615833562@arcas>
Subject: [jira] [Commented] (HIVE-4331) Integrated StorageHandler for Hive
 and HCat using the HiveStorageHandler
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ashutosh Chauhan commented on HIVE-4331:
----------------------------------------

I see what you are saying and I agree HiveOF interface is burdensome. What I am wondering is if we can morph HiveOFImpl into something which can serve this requirement, so that we don't have plethora of classes trying to wrap OFs in Hive at various point in lifecycle. How about we make HiveOFImpl implement HiveOF and than add implementation for getHiveRR and getRR in it in similar fashion in whats in proposed HivePTOF is? 
                
> Integrated StorageHandler for Hive and HCat using the HiveStorageHandler
> ------------------------------------------------------------------------
>
>                 Key: HIVE-4331
>                 URL: https://issues.apache.org/jira/browse/HIVE-4331
>             Project: Hive
>          Issue Type: Task
>          Components: HCatalog
>    Affects Versions: 0.11.0, 0.12.0
>            Reporter: Ashutosh Chauhan
>            Assignee: Viraj Bhat
>         Attachments: HIVE4331_07-17.patch, StorageHandlerDesign_HIVE4331.pdf
>
>
> 1) Deprecate the HCatHBaseStorageHandler and "RevisionManager" from HCatalog. These will now continue to function but internally they will use the "DefaultStorageHandler" from Hive. They will be removed in future release of Hive.
> 2) Design a HivePassThroughFormat so that any new StorageHandler in Hive will bypass the HiveOutputFormat. We will use this class in Hive's "HBaseStorageHandler" instead of the "HiveHBaseTableOutputFormat".
> 3) Write new unit tests in the HCat's "storagehandler" so that systems such as Pig and Map Reduce can use the Hive's "HBaseStorageHandler" instead of the "HCatHBaseStorageHandler".
> 4) Make sure all the old and new unit tests pass without backward compatibility (except known issues as described in the Design Document).
> 5) Replace all instances of the HCat source code, which point to "HCatStorageHandler" to use the"HiveStorageHandler" including the "FosterStorageHandler".
> I have attached the design document for the same and will attach a patch to this Jira.

--
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