[
https://issues.apache.org/jira/browse/HIVE-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605435#comment-13605435
]
Alan Gates commented on HIVE-4198:
----------------------------------
The HCatalog code needs to be moved into Hive from the incubator. This will be
done by an 'svn mv' command in order to preserve history. I propose to do this
as follows:
# I will move all of the hcat code as is under the hcatalog stub directory
created in HIVE-4145. I will put it into a sub-directory to avoid clashes with
files names that have already been created (such as build.xml). The command
for this will look like: 'svn mv
https://svn.apache.org/repos/asf//incubator/hcatalog/trunk
https://svn.apache.org/repos/asf//hive/trunk/hcatalog/hcat-code-dump' This is
a call on the repo and cannot be uploaded as a patch to JIRA.
# I can then deal with the files in that directory in separate commits.
## DISCLAIMER.txt can be removed as HCat is no longer incubating
## KEYS, LICENSE.txt, and NOTICE.TXT can be merged with the top level Hive
files, as HCat no longer needs to track these entities separately.
## I propose we put CHANGES.txt, README.txt, and RELEASE_NOTES.txt in an newly
created 'pre-hive-archive' directory. Going forward HCat will no longer need
separate versions of these files. But for the sake of history it would be nice
to keep them around.
## build.xml will be merged with the build.xml that was created in HIVE-4145
## The other directories and files will be moved to the top level.
## The Java code in these directories will be refactored into
org.apache.hive.hcatalog and stub classes for org.apache.hcatalog classes will
be created. This will only be done for classes available through public APIs.
I further propose that for the duration of these operations only, the hcatalog
directory will be CTR (commit then review) so that I do not have to post
patches and wait for a review for each of these file move/merge operations. I
will have JIRAs for each of these operations so that they are trackable in the
future.
I am proposing this double hop (move to hcat-code-dump and then from there) for
two reasons. One, trying to do this in one patch is not doable based on how
svn mv works. Two, it will be much easier to track and understand what is
happening (both now and for users in the future reading the svn history) if it
is done in a set of discrete steps rather than in one mega-move that also
removes, moves, and merges files and directories.
> Move HCatalog code into Hive
> ----------------------------
>
> Key: HIVE-4198
> URL: https://issues.apache.org/jira/browse/HIVE-4198
> Project: Hive
> Issue Type: Task
> Components: HCatalog
> Affects Versions: 0.11.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Fix For: 0.11.0
>
>
> The HCatalog code needs to be moved into Hive.
--
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
