hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lefty Leverenz <leftylever...@gmail.com>
Subject Re: Timeline for release of Hive 0.14
Date Tue, 23 Sep 2014 21:04:54 GMT
HIVE-6586 <https://issues.apache.org/jira/browse/HIVE-6586> - Add new
parameters to HiveConf.java after commit HIVE-6037


This updates many parameter descriptions.  A patch is available but it
needs rebasing and review.


I added 0.14.0 to the fix version.



-- Lefty

On Tue, Sep 23, 2014 at 4:49 PM, Thejas Nair <thejas@hortonworks.com> wrote:

> HIVE-7615 - Beeline should have an option for user to see the query
> progress
> This is a very useful feature change, brings beeline closer to hive
> cli in terms of features. It has patches, the patch needs to be
> updated to address review comments.
>
> HIVE-8221 - authorize additional metadata read operations in metastore
> storage based authorization
> I should have a patch for this later today.
>
> HIVE-7919 - sql std auth: user with 'admin option' for role should be
> able to list all users in the role
> I will have a patch for this one in a day  or two.
>
> I have updated the fix version of the above to 0.14.0 .
>
>
>
> On Tue, Sep 23, 2014 at 1:39 PM, Vikram Dixit <vikram@hortonworks.com>
> wrote:
> > Hi Folks,
> >
> > I have added all the bugs to the list that had affects version set to
> > 0.14.0 similar to the status page of 0.13.0. This will help track and
> nail
> > down the fixes we need to get the release going. I request all devs to go
> > through their jiras and let me know if any of them are critical or
> blockers
> > that need to be included in 0.14.0. Please mark fix versions to be 0.14.0
> > for those.
> >
> > Thanks
> > Vikram.
> >
> > On Tue, Sep 23, 2014 at 12:53 PM, Jason Dere <jdere@hortonworks.com>
> wrote:
> >
> >> Would like to see HIVE-8102 and HIVE-7971 in if possible.
> >>
> >> Thanks,
> >> Jason
> >>
> >> On Sep 23, 2014, at 12:33 PM, Lars Francke <lars.francke@gmail.com>
> wrote:
> >>
> >> > Hi Vikram,
> >> >
> >> > I'd like to add HIVE-7107[1] to the list. Ashutosh voted against
> >> including
> >> > it but that was based on the premise that HiveServer1 would be removed
> >> > which doesn't seem to happen in this release. So I'd like to get this
> in
> >> as
> >> > it's a very annoying issue to debug in production. It is in need of a
> >> > review. Any volunteers?
> >> >
> >> > I'll take a look at the patch and will rebase if needed.
> >> >
> >> > Cheers,
> >> > Lars
> >> >
> >> > [1] <https://issues.apache.org/jira/browse/HIVE-7107>
> >> >
> >> > On Tue, Sep 23, 2014 at 9:16 PM, Vikram Dixit <vikram@hortonworks.com
> >
> >> > wrote:
> >> >
> >> >> Hi Folks,
> >> >>
> >> >> I have created a wiki page for tracking 0.14 release:
> >> >>
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.14+release+status
> >> >>
> >> >> Please take a look and let me know if I have to add any more jiras
to
> >> the
> >> >> list. Given that the CBO branch is close to getting merged and the
> >> progress
> >> >> being made there, I will branch in a day or so once that commit goes
> in.
> >> >>
> >> >> Thanks
> >> >> Vikram.
> >> >>
> >> >> On Fri, Sep 12, 2014 at 12:15 AM, Navis류승우 <navis.ryu@nexr.com>
> wrote:
> >> >>
> >> >>> Hi,
> >> >>>
> >> >>> I'll really appreciate if HIVE-5690 can be included, which becomes
> >> harder
> >> >>> and harder to rebase.
> >> >>> Other 79 patches I've assigned to can be held on.
> >> >>>
> >> >>> Thanks,
> >> >>> Navis
> >> >>>
> >> >>>
> >> >>> 2014-09-11 19:54 GMT+09:00 Vaibhav Gumashta <
> vgumashta@hortonworks.com
> >> >:
> >> >>>
> >> >>>> Hi Vikram,
> >> >>>>
> >> >>>> Can we also add: https://issues.apache.org/jira/browse/HIVE-6799
&
> >> >>>> https://issues.apache.org/jira/browse/HIVE-7935 to the list.
> >> >>>>
> >> >>>> Thanks,
> >> >>>> --Vaibhav
> >> >>>>
> >> >>>> On Wed, Sep 10, 2014 at 12:18 AM, Satish Mittal <
> >> >>> satish.mittal@inmobi.com>
> >> >>>> wrote:
> >> >>>>
> >> >>>>> Hi,
> >> >>>>> Can you please include HIVE-7892 (Thrift Set type not working
with
> >> >>> Hive)
> >> >>>> as
> >> >>>>> well? It is under code review.
> >> >>>>>
> >> >>>>> Regards,
> >> >>>>> Satish
> >> >>>>>
> >> >>>>>
> >> >>>>> On Tue, Sep 9, 2014 at 2:10 PM, Suma Shivaprasad <
> >> >>>>> sumasai.shivaprasad@gmail.com> wrote:
> >> >>>>>
> >> >>>>>> 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 <
> gates@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 <dcarol@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 . <amareshwari@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 <vikram@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
<
> >> >>>> hashutosh@apache.org
> >> >>>>>>
> >> >>>>>>> <hashutosh@apache.org>
> >> >>>>>>>
> >> >>>>>>>  Ashutosh Chauhan <hashutosh@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.francke@gmail.com>
> >> >>>>>>> <lars.francke@gmail.com>
> >> >>>>>>>
> >> >>>>>>>  Lars Francke <lars.francke@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.
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>> _____________________________________________________________
> >> >>>>> The information contained in this communication is intended
solely
> >> >> for
> >> >>>> the
> >> >>>>> use of the individual or entity to whom it is addressed
and others
> >> >>>>> authorized to receive it. It may contain confidential or
legally
> >> >>>> privileged
> >> >>>>> information. If you are not the intended recipient you
are hereby
> >> >>>> notified
> >> >>>>> that any disclosure, copying, distribution or taking any
action in
> >> >>>> reliance
> >> >>>>> on the contents of this information is strictly prohibited
and
> may be
> >> >>>>> unlawful. If you have received this communication in error,
please
> >> >>> notify
> >> >>>>> us immediately by responding to this email and then delete
it from
> >> >> your
> >> >>>>> system. The firm is neither liable for the proper and complete
> >> >>>> transmission
> >> >>>>> of the information contained in this communication nor
for any
> delay
> >> >> in
> >> >>>> its
> >> >>>>> receipt.
> >> >>>>>
> >> >>>>
> >> >>>> --
> >> >>>> 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.
> >>
> >
> > --
> > 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.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message