Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hive, mail # dev - creating branch 0.12


Copy link to this message
-
Re: creating branch 0.12
Ashutosh Chauhan 2013-09-08, 05:38
Hi Thejas,
Will you please consider following couple of issues for inclusion in 0.12.

a) HIVE-4492 : breaks backward compatibility for metastore thrift api. Also
subsequently resulted in HIVE-4930
b) HIVE-5056 : is functional outage.

a) Available patch doesn't apply cleanly anymore. I am working on rebasing
it.
b) is under review.

Hopefully, both will be available in time.

Thanks,
Ashutosh

On Fri, Sep 6, 2013 at 6:38 PM, Thejas Nair <[EMAIL PROTECTED]> wrote:

> Hive 0.12 branch has been created! (branch-0.12)
>
>
>
> On Fri, Sep 6, 2013 at 5:29 PM, Thejas Nair <[EMAIL PROTECTED]>
> wrote:
> > As discussed in earlier thread, I will go ahead and create a branch
> > for hive 0.12 release. I will do that in another hour.
> >
> > Please reply to this thread if there are any jiras that are not
> > committed yet, that you feel should be included in hive 0.12.  Please
> > include only jiras that are being actively worked on (or that you are
> > willing to actively work on), and those that are likely to able to get
> > to a committable state in another week or so. I would like to get 0.12
> > into a stabilizing phase in two weeks, which would mean freezing the
> > branch at that point to checkin only any blocker bug fixes.
> >
> > Thanks,
> > Thejas
>
> --
> 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.
>