On Mar 18, 2013, at 12:06 PM, Mithun Radhakrishnan wrote:

> Hello, Alan. Thanks for getting this going.
> 
> From HIVE-4145, it looks like HCatalog trunk code is moving into hive-trunk, 
> and the HCatalog release branches stay where they are. Is that right? (It 
> would make sense not to destabilize the current releases for this. Moving 
> into Hive is a fairly tectonic event. :])

I've replied to the issues of moving the branches on HIVE-4145.  

> 
> Arup and I have a couple of patches in flight:
> 1. https://issues.apache.org/jira/browse/HCATALOG-609: Atomic AddPartition 
> event. Depends on HIVE-3938 (Hive metastore changes for the same).

I'm happy to check in 609 if 3938 goes in.  But I don't have the ability to 
check that in.  You'll have to convince one of the Hive committers to take a 
look.  I don't want to hold the move for it though.

> 2. https://issues.apache.org/jira/browse/HCATALOG-627: Thread-safety for 
> NotificationListener.
> (Preferably in that order.)

If I can't get 609 in before the move do you still want this in, or would you 
prefer it wait?

Alan.

> 
> If HCatalog release branches aren't being moved, then we can get those 
> patches into branch-5 even after HCat-trunk has moved into Hive-trunk.
> 
> Mithun
> 
> 
> ________________________________
> From: Alan Gates <[email protected]>
> To: [email protected] 
> Sent: Monday, March 18, 2013 11:32 AM
> Subject: Proposal for moving HCat code into Hive
> 
> In JIRA https://issues.apache.org/jira/browse/HIVE-4145 Carl has created the 
> stub directory for HCatalog in the Hive repository.  I have published a 
> proposal for how to move the code in 
> https://issues.apache.org/jira/browse/HIVE-4198  Comments are welcome there.  
> 
> Once this move is done all patches against HCat will be invalid and will 
> require regeneration.  I will attempt today and tomorrow to check-in, review, 
> or return to open all JIRAs that currently are patch available in order to 
> avoid invalidating them.  Assuming my proposal in HIVE-4198 is accepted I 
> will then need to lock down the repo for a day or two until I get all of the 
> moving around done.
> 
> Alan.

Reply via email to