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,

Damien CAROL

 * tél : +33 (0)4 74 96 88 14
 * fax : +33 (0)4 74 96 31 88
 * email :dca...@blitzbs.com <mailto:dca...@blitzbs.com>

BLITZ BUSINESS SERVICE

Le 08/09/2014 12:08, amareshwarisr . a écrit :
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


On Sat, Sep 6, 2014 at 6:23 AM, Vikram Dixit <vik...@hortonworks.com> wrote:

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>
wrote:

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>
wrote:

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>
[1] <https://issues.apache.org/jira/browse/HIVE-6977>
[2] <https://issues.apache.org/jira/browse/HIVE-6123>
[3] <https://issues.apache.org/jira/browse/HIVE-7622>
[4] <https://issues.apache.org/jira/browse/HIVE-7543>

On Fri, Aug 22, 2014 at 11:01 PM, John Pullokkaran <
jpullokka...@hortonworks.com> wrote:

We are working on Hive-5775 (Cost Based Optimizer), we hope to get
this
in
to Hive 14.

Thanks
John


On Thu, Aug 21, 2014 at 11:53 PM, Lefty Leverenz <
leftylever...@gmail.com>
wrote:

Release 0.14 should include HIVE-6586
<https://issues.apache.org/jira/browse/HIVE-6586> (various fixes
to
HiveConf.java parameters).  I'll do that as soon as possible.

72 jiras have the TODOC14 label now, although my own tally is 99.
This
is
more than mere mortals can accomplish in a few weeks.  Therefore I
recommend that you all plead with your managers to allocate some
tech-writer resources to Hive wikidocs for the 0.14.0 release.

I'll send out a state-of-the-docs message in a separate thread.

-- Lefty


On Fri, Aug 22, 2014 at 2:28 AM, Alan Gates <ga...@hortonworks.com
wrote:
+1, Eugene and I are working on getting HIVE-5317 (insert,
update,
delete)
done and would like to get it in.

Alan.

   Nick Dimiduk <ndimi...@gmail.com>
  August 20, 2014 at 12:27
It'd be great to get HIVE-4765 included in 0.14. The proposed
changes
are a
big improvement for us HBase folks. Would someone mind having a
look
in
that direction?

Thanks,
Nick



   Thejas Nair <the...@hortonworks.com>
  August 19, 2014 at 15:20
+1
Sounds good to me.
Its already almost 4 months since the last release. It is time to
start preparing for the next one.
Thanks for volunteering!


   Vikram Dixit <vik...@hortonworks.com>
  August 19, 2014 at 14:02
Hi Folks,

I was thinking that it was about time that we had a release of
hive
0.14
given our commitment to having a release of hive on a periodic
basis.
We
could cut a branch and start working on a release in say 2 weeks
time
around September 5th (Friday). After branching, we can focus on
stabilizing
for the release and hopefully have an RC in about 2 weeks post
that.
I
would like to volunteer myself for the duties of the release
manager
for
this version if the community agrees.

Thanks
Vikram.


--
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.

--
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