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 the Hive 0.13 release?
Date Wed, 09 Apr 2014 08:15:10 GMT
> how much effort it would take to do HIVE-6586

One day of concentrated effort, but call it two days just in case I'm not
concentrating.  (Spring fever on the East Coast, where spring is a big
deal.)

> Regarding the missing params in hive-default:

I can take care of that, thanks -- I've been flagging them in the mailing
list.  But if you have a good way to check, let's both do it.

> What will it take to rebase.

That's a question for Navis.  I was assuming we would stick with the
current patch and HIVE-6586 would update HiveConf.java.

> Wasn't it reverted from the 0.13 branch? Don't recall the reason for
this. Is that issue resolved now?

Yes, there was a build issue (see Feb. 18th
comments<https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904584#comment-13904584>)
and AFAIK the issue is resolved now (see comments on Feb.
23<https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909988#comment-13909988>,
Feb. 25<https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912461#comment-13912461>,
and Feb. 26-a<https://issues.apache.org/jira/browse/HIVE-6037?focusedCommentId=13913412&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13913412>
...
but also Feb. 26-b,<https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913449#comment-13913449>
Feb.
27<https://issues.apache.org/jira/browse/HIVE-6037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914135#comment-13914135>,
and March 12<https://issues.apache.org/jira/browse/HIVE-6037?focusedCommentId=13932785&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13932785>
's patch for 0.13.0<https://issues.apache.org/jira/secure/attachment/12634329/HIVE-6037-0.13.0>
--
I had to add ".txt" for missing line breaks).

Thanks.


-- Lefty


On Wed, Apr 9, 2014 at 2:49 AM, Harish Butani <hbutani@hortonworks.com>wrote:

> Lefty, good point.
> I was assuming 6037 is not going into 0.13.  Wasn't it reverted from the
> 0.13 branch?
> Don't recall the reason for this. Is that issue resolved now?
> The last patch is from March 12th. What will it take to rebase.
>
> Seems safer to keep out of 0.13 and manually add the missing params.
> But I will let the experts weigh in.
> Regarding the missing params in hive-default: will try to get  you the
> missing ones by tomorrow.
> If we decide to go with adding 6037 to 0.13: do you have a sense of how
> much effort it would take to do HIVE-6586.
>
> regards,
> Harish.
>
> On Apr 8, 2014, at 11:02 PM, Lefty Leverenz <leftyleverenz@gmail.com>
> wrote:
>
> > What about HIVE-6037 <https://issues.apache.org/jira/browse/HIVE-6037>
> > (Synchronize
> > HiveConf with hive-default.xml.template and support show conf) and its
> > followup HIVE-6586 <https://issues.apache.org/jira/browse/HIVE-6586>?
> >
> > Some new configs probably don't have definitions in
> > hive-defaul.xml.template because I've been telling people not to bother
> > with the template file, since it's going to be generated from
> HiveConf.java
> > soon.  So if HIVE-6037 and -6586 aren't in 0.13.0, I'll have to create
> > another jira for 0.13.0 to patch the template file.
> >
> > But if HIVE-6037 is in 0.13.0, then I have a fair amount of work to do on
> > HIVE-6586 -- otherwise several new configs won't be in HiveConf.java.
> >
> > -- Lefty
> >
> >
> > On Wed, Apr 9, 2014 at 1:33 AM, Harish Butani <hbutani@hortonworks.com
> >wrote:
> >
> >> Hi,
> >>
> >> We are getting close to having all the issues resolved.
> >> I have the following list of open jiras as needing to go into 0.13
> >> 6863, 5687, 6604,6850,6818,6732,4904,5376, and 6319.
> >>
> >> These are all close to being committed. Some are waiting for the 24hr
> >> period, a couple have been reviewed and +1ed, waiting for tests to pass.
> >>
> >> So lets shoot for closing out all these issues by Thursday 12pm PST.
> >> Would like to cut an rc by Thursday afternoon.
> >>
> >> regards,
> >> Harish.
> >>
> >>
> >> On Mar 26, 2014, at 7:14 PM, Prasanth Jayachandran <
> >> pjayachandran@hortonworks.com> wrote:
> >>
> >>> Hi Harish
> >>>
> >>> Can we have the following bugs for 0.13? These bugs are related to
> >> feature HIVE-6455 added as part of 0.13.
> >>> https://issues.apache.org/jira/browse/HIVE-6748 (Resource leak bug)
> >>> https://issues.apache.org/jira/browse/HIVE-6760 (Bug in handling list
> >> bucketing)
> >>> https://issues.apache.org/jira/browse/HIVE-6761 (Bug with hashcodes
> >> generation)
> >>>
> >>> Thanks
> >>> Prasanth Jayachandran
> >>>
> >>> On Mar 26, 2014, at 1:22 PM, Hari Subramaniyan <
> >> hsubramaniyan@hortonworks.com> wrote:
> >>>
> >>>> Hi Harish
> >>>> Can you include HIVE-6708. It covers quite a number of issues
> associated
> >>>> with Vectorization(including some correctness issues and exceptions).
> >>>>
> >>>> Thanks
> >>>> Hari
> >>>>
> >>>>
> >>>> On Tue, Mar 25, 2014 at 12:01 PM, Xuefu Zhang <xzhang@cloudera.com>
> >> wrote:
> >>>>
> >>>>> Harish,
> >>>>>
> >>>>> Could we include HIVE-6740?
> >>>>>
> >>>>> Thanks,
> >>>>> Xuefu
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 20, 2014 at 7:27 PM, Prasanth Jayachandran <
> >>>>> pjayachandran@hortonworks.com> wrote:
> >>>>>
> >>>>>> Harish,
> >>>>>>
> >>>>>> Could you add the following bugs as well?
> >>>>>> Following are related to LazyMap bug
> >>>>>> https://issues.apache.org/jira/browse/HIVE-6707
> >>>>>> https://issues.apache.org/jira/browse/HIVE-6714
> >>>>>> https://issues.apache.org/jira/browse/HIVE-6711
> >>>>>>
> >>>>>> Following is NPE bug with orc struct
> >>>>>> https://issues.apache.org/jira/browse/HIVE-6716
> >>>>>>
> >>>>>> Thanks
> >>>>>> Prasanth Jayachandran
> >>>>>>
> >>>>>> On Mar 14, 2014, at 6:26 PM, Eugene Koifman <
> ekoifman@hortonworks.com
> >>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> could you add
> https://issues.apache.org/jira/browse/HIVE-6676please.
> >>>>>> It's
> >>>>>>> a blocker as well.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Eugene
> >>>>>>>
> >>>>>>>
> >>>>>>> On Fri, Mar 14, 2014 at 5:30 PM, Vaibhav Gumashta <
> >>>>>> vgumashta@hortonworks.com
> >>>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Harish,
> >>>>>>>>
> >>>>>>>> Can we have this in as well:
> >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6660.
> >>>>>>>> Blocker bug in my opinion.
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> --Vaibhav
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Fri, Mar 14, 2014 at 2:21 PM, Thejas Nair <
> >> thejas@hortonworks.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Harish,
> >>>>>>>>> Can you also include  HIVE-6673<
> >>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6673>
> >>>>>>>>> -  show grant statement for all principals throws
NPE
> >>>>>>>>> This variant of 'show grant' is very useful, and
the fix for NPE
> is
> >>>>>>>>> straightforward. It is patch available now.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Fri, Mar 14, 2014 at 10:25 AM, Yin Huai <
> huaiyin.thu@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Guys,
> >>>>>>>>>>
> >>>>>>>>>> Seems ConditionalResolverCommonJoin is not working
correctly? I
> >>>>>> created
> >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6668
and set it as a
> >>>>>>>> blocker.
> >>>>>>>>>>
> >>>>>>>>>> thanks,
> >>>>>>>>>>
> >>>>>>>>>> Yin
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Fri, Mar 14, 2014 at 11:34 AM, Thejas Nair
<
> >>>>> thejas@hortonworks.com
> >>>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Can you also add HIVE-6647 <
> >>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6647>
to
> >>>>>>>>>>> the list? It is marked as a blocker for
0.13.
> >>>>>>>>>>> It has a necessary version number upgrade
for HS2. It is ready
> to
> >>>>> be
> >>>>>>>>>>> committed.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Mar 14, 2014 at 12:38 AM, Prasanth
Jayachandran <
> >>>>>>>>>>> pjayachandran@hortonworks.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Harish
> >>>>>>>>>>>>
> >>>>>>>>>>>> Can you please make the following changes
to my earlier
> request?
> >>>>>>>>>>>>
> >>>>>>>>>>>> HIVE-4177 is not required.. instead
the same work is tracked
> >> under
> >>>>>>>>>>>> HIVE-6578.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Can you also consider HIVE-6656?
> >>>>>>>>>>>> HIVE-6656 is bug fix for ORC reader
when reading timestamp
> >>>>>>>>> nanoseconds.
> >>>>>>>>>>>> This bug exists in earlier versions
as well, so it will be
> good
> >>>>>>>> have
> >>>>>>>>>> this
> >>>>>>>>>>>> fixed in 0.13.0
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks
> >>>>>>>>>>>> Prasanth Jayachandran
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Mar 13, 2014, at 8:52 AM, Thejas
Nair <
> >> thejas@hortonworks.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Harish,
> >>>>>>>>>>>>> I think we should include the following
-
> >>>>>>>>>>>>> HIVE-6547 - This is a cleanup of
metastore api changes
> >> introduced
> >>>>>>>>> in
> >>>>>>>>>>>> 0.13 .
> >>>>>>>>>>>>> This can't be done post release.
I will get a patch out in
> few
> >>>>>>>>> hours.
> >>>>>>>>>>>>> HIVE-6567 -  fixes a NPE in 'show
grant .. on all"
> >>>>>>>>>>>>> HIVE-6629 - change in syntax for
'set role none' . marked as
> a
> >>>>>>>>>> blocker
> >>>>>>>>>>>> bug.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Mar 11, 2014 at 8:39 AM,
Harish Butani <
> >>>>>>>>>>> hbutani@hortonworks.com
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> yes sure.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Mar 10, 2014, at 3:55 PM,
Gopal V <gopalv@apache.org>
> >> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Can I add HIVE-6518 as well
to the merge queue on
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> It is a relatively simple
OOM safety patch to vectorized
> >>>>>>>>> group-by.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Tests pass locally for vec
group-by, but the pre-commit
> tests
> >>>>>>>>>> haven't
> >>>>>>>>>>>>>> fired eventhough it's been PA
for a while now.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Cheers,
> >>>>>>>>>>>>>>> Gopal
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> 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.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> 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.
> >>
> >>
> >> --
> >> 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