Please include https://issues.apache.org/jira/browse/HIVE-7694 as well. It
is currently under review by Amareshwari and should be done in the next
couple of days.

Thanks
Suma


On Mon, Sep 8, 2014 at 5:44 PM, Alan Gates <ga...@hortonworks.com> wrote:

> I'll review that.  I just need the time to test it against mysql, oracle,
> and hopefully sqlserver.  But I think we can do this post branch if we need
> to, as it's a bug fix rather than a feature.
>
> Alan.
>
>   Damien Carol <dca...@blitzbs.com>
>  September 8, 2014 at 3:19
>  Same request for https://issues.apache.org/jira/browse/HIVE-7689
>
> I already provided a patch, re-based it many times and I'm waiting for a
> review.
>
> Regards,
>
> Le 08/09/2014 12:08, amareshwarisr . a écrit :
>
>   amareshwarisr . <amareshw...@gmail.com>
>  September 8, 2014 at 3:08
> Would like to include https://issues.apache.org/jira/browse/HIVE-2390 and
> https://issues.apache.org/jira/browse/HIVE-7936.
>
> I can review and merge them.
>
> Thanks
> Amareshwari
>
>
>
>   Vikram Dixit <vik...@hortonworks.com>
>  September 5, 2014 at 17:53
> Hi Folks,
>
> I am going to start consolidating the items mentioned in this list and
> create a wiki page to track it. I will wait till the end of next week to
> create the branch taking into account Ashutosh's request.
>
> Thanks
> Vikram.
>
>
> On Fri, Sep 5, 2014 at 5:39 PM, Ashutosh Chauhan <hashut...@apache.org>
> <hashut...@apache.org>
>
>   Ashutosh Chauhan <hashut...@apache.org>
>  September 5, 2014 at 17:39
> Vikram,
>
> Some of us are working on stabilizing cbo branch and trying to get it
> merged into trunk. We feel we are close. May I request to defer cutting the
> branch for few more days? Folks interested in this can track our progress
> here : https://issues.apache.org/jira/browse/HIVE-7946
>
> Thanks,
> Ashutosh
>
>
> On Fri, Aug 22, 2014 at 4:09 PM, Lars Francke <lars.fran...@gmail.com>
> <lars.fran...@gmail.com>
>
>   Lars Francke <lars.fran...@gmail.com>
>  August 22, 2014 at 16:09
> Thank you for volunteering to do the release. I think a 0.14 release is a
> good idea.
>
> I have a couple of issues I'd like to get in too:
>
> * Either HIVE-7107[0] (Fix an issue in the HiveServer1 JDBC driver) or
> HIVE-6977[1] (Delete HiveServer1). The former needs a review the latter a
> patch
> * HIVE-6123[2] Checkstyle in Maven needs a review
>
> HIVE-7622[3] & HIVE-7543[4] are waiting for any reviews or comments on my
> previous thread[5]. I'd still appreciate any helpers for reviews or even
> just comments. I'd feel very sad if I had done all that work for nothing.
> Hoping this thread gives me a wider audience. Both patches fix up issues
> that should have been caught in earlier reviews as they are almost all
> Checkstyle or other style violations but they make for huge patches. I
> could also create hundreds of small issues or stop doing these things
> entirely
>
>
>
> [0] <https://issues.apache.org/jira/browse/HIVE-7107>
> <https://issues.apache.org/jira/browse/HIVE-7107>
> [1] <https://issues.apache.org/jira/browse/HIVE-6977>
> <https://issues.apache.org/jira/browse/HIVE-6977>
> [2] <https://issues.apache.org/jira/browse/HIVE-6123>
> <https://issues.apache.org/jira/browse/HIVE-6123>
> [3] <https://issues.apache.org/jira/browse/HIVE-7622>
> <https://issues.apache.org/jira/browse/HIVE-7622>
> [4] <https://issues.apache.org/jira/browse/HIVE-7543>
> <https://issues.apache.org/jira/browse/HIVE-7543>
>
> On Fri, Aug 22, 2014 at 11:01 PM, John Pullokkaran <
>
>
> --
> Sent with Postbox <http://www.getpostbox.com>
>
> 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