As an update, it is now 6pm PDT on September 5th, and we're now done
with the changes in HIVE-4895 and HIVE-4896.

However, there is one more issue we found along the way, and that's
addressed by HIVE-5233 which I still have to review before committing.

hcatalog/ itself can be considered unfrozen, but we still need to
consider hcatalog/storage-handlers/hbase/ frozen till 11:59pm PDT on
September 5th.

Since this directory only deals with code that is now considered
deprecated, I hope it won't affect anyone (except Viraj from
HIVE-4331) but that patch is not in a patch-available state.



On Tue, Sep 3, 2013 at 6:50 PM, Sushanth Sowmyan <khorg...@gmail.com> wrote:
> Sounds good, go for it. Any hcatalog patch-available patches that we
> do not get in by 8AM PDT will have to be canceled and regenerated.
> I'll do that tomorrow.
>
> On Tue, Sep 3, 2013 at 6:34 PM, Eugene Koifman <ekoif...@hortonworks.com> 
> wrote:
>> Yes, that is correct.
>>
>>
>> On Tue, Sep 3, 2013 at 6:28 PM, Thejas Nair <the...@hortonworks.com> wrote:
>>
>>> Eugene,
>>> I assume you want the hold off on checkins to hive/hcatalog dir to
>>> start from tomorrow AM pacific time (Sept 4) (say 8 am PDT ?) and you
>>> expect you changes to be done by Sept 5 around 6pm Pacific time. Is
>>> that correct ?
>>>
>>> Thanks,
>>> Thejas
>>>
>>>
>>>
>>> On Tue, Sep 3, 2013 at 6:00 PM, Eugene Koifman <ekoif...@hortonworks.com>
>>> wrote:
>>> > Hi,
>>> >
>>> > the work on 2 items (described in detail earlier on this mail list) below
>>> > will start tomorrow. Please avoid checking anything into hive/hcatalog. I
>>> > expect this to be complete by EOD Thursday.
>>> >
>>> >
>>> > 1. HIVE-4895 - change package name from org.apache.hcatalog to
>>> > org.apache.hive.hcatalog
>>> >
>>> > 2. HIVE-4896 - create binary (API) backwards compatibility layer for hcat
>>> > users upgrading from 0.11 to 0.12
>>> >
>>> >
>>> > Thank you,
>>> >
>>> > Eugene
>>> >
>>> > --
>>> > CONFIDENTIALITY NOTICE
>>> > NOTICE: This message is intended for the use of the individual or entity
>>> to
>>> > which it is addressed and may contain information that is confidential,
>>> > privileged and exempt from disclosure under applicable law. If the reader
>>> > of this message is not the intended recipient, you are hereby notified
>>> that
>>> > any printing, copying, dissemination, distribution, disclosure or
>>> > forwarding of this communication is strictly prohibited. If you have
>>> > received this communication in error, please contact the sender
>>> immediately
>>> > and delete it from your system. Thank You.
>>>
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender immediately
>> and delete it from your system. Thank You.

Reply via email to