Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 18 Apr 2013 23:31:16 +0000 (UTC)
From: "Alan Gates (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12639868.1364584130205.189976.1366327876249@arcas>
In-Reply-To: <JIRA.12639868.1364584130205@arcas>
References: <JIRA.12639868.1364584130205@arcas>
Subject: [jira] [Commented] (HIVE-4266) Refactor HCatalog code to
 org.apache.hive.hcatalog
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alan Gates commented on HIVE-4266:
----------------------------------

We cannot make this kind of backwards incompatible change for users.  Users will not see this as "here, run this script against your source tree."  They'll see it as they have to go modify, re-test, and re-deploy every application.

We should not make this a blocker for 0.11.  I'm 90% of the way through the patch, but it will take a fair amount of testing when I'm done to asure that it works with both org.apache.hcatalog and org.apache.hive.hcatalog.


> Refactor HCatalog code to org.apache.hive.hcatalog
> --------------------------------------------------
>
>                 Key: HIVE-4266
>                 URL: https://issues.apache.org/jira/browse/HIVE-4266
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HCatalog
>    Affects Versions: 0.11.0
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Blocker
>             Fix For: 0.11.0
>
>
> Currently HCatalog code is in packages org.apache.hcatalog.  It needs to now move to org.apache.hive.hcatalog.  Shell classes/interface need to be created for public facing classes so that user's code does not break.

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