You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by Harish Butani <hb...@hortonworks.com> on 2014/03/04 04:53:48 UTC
Re: Timeline for the Hive 0.13 release?
I plan to create the branch 5pm PST tomorrow.
Ok with everybody?
regards,
Harish.
On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com> wrote:
> That's appropriate -- let the Hive release march forth on March 4th.
>
>
> -- Lefty
>
>
> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <hb...@hortonworks.com>wrote:
>
>> Ok,let’s set it for March 4th .
>>
>> regards,
>> Harish.
>>
>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com> wrote:
>>
>>> Might as well make it March 4th or 5th. Otherwise folks will burn
>>> weekend time to get patches in.
>>>
>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <hb...@hortonworks.com>
>> wrote:
>>>> Yes makes sense.
>>>> How about we postpone the branching until 10am PST March 3rd, which is
>> the following Monday.
>>>> Don’t see a point of setting the branch time to a Friday evening.
>>>> Do people agree?
>>>>
>>>> regards,
>>>> Harish.
>>>>
>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <th...@hortonworks.com>
>> wrote:
>>>>>> Can we wait for some few more days for the branching ? I have a few
>> more
>>>>>> security fixes that I would like to get in, and we also have a long
>>>>>> pre-commit queue ahead right now. How about branching around Friday
>> next
>>>>>> week ? By then hadoop 2.3 should also be out as that vote has been
>>>>>> concluded, and we can get HIVE-6037 in as well.
>>>>>> -Thejas
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <br...@cloudera.com>
>> wrote:
>>>>>>
>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
>> pending
>>>>>>> tests.
>>>>>>>
>>>>>>> Brock
>>>>>>>
>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
>> wrote:
>>>>>>>> HIVE-6037 is for generating hive-default.template file from
>> HiveConf.
>>>>>>> Could
>>>>>>>> it be included in this release? If it's not, I'll suspend further
>>>>>>> rebasing
>>>>>>>> of it till next release (conflicts too frequently).
>>>>>>>>
>>>>>>>>
>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <leftyleverenz@gmail.com
>>> :
>>>>>>>>
>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0 patches in
>> time
>>>>>>> for
>>>>>>>>> the release. It's a long and growing list, though, so no promises.
>>>>>>>>>
>>>>>>>>> Feel free to do your own documentation, or hand it off to a
>> friendly
>>>>>>>>> in-house writer.
>>>>>>>>>
>>>>>>>>> -- Lefty, self-appointed Hive docs maven
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
>> thejas@hortonworks.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Sounds good to me.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to cut a
>>>>>>> branch.
>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
>>>>>>>>>>> The goal is to keep the release cycle short: couple of weeks; so
>>>>>>> after
>>>>>>>>>> the
>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking in
>> only
>>>>>>>>>>> blocker/critical bug fixes.
>>>>>>>>>>>
>>>>>>>>>>> regards,
>>>>>>>>>>> Harish.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <br...@cloudera.com>
>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I agree that picking a date to branch and then restricting
>>>>>>> commits to
>>>>>>>>>>> that
>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
>>>>>>>>>>>>
>>>>>>>>>>>> Brock
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
>>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Yes agree it is time to start planning for the next release.
>>>>>>>>>>>>> I would like to volunteer to do the release management duties
>> for
>>>>>>>>> this
>>>>>>>>>>>>> release(will be a great experience for me)
>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> regards,
>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
>> thejas@hortonworks.com
>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
>> release.
>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted patches
>>>>>>> that
>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
>> phase
>>>>>>> of
>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
>>>>>>> laborious.
>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to get any
>>>>>>>>>> patches
>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take in
>>>>>>> only
>>>>>>>>>>>>>> critical bug fixes to the branch after that.
>>>>>>>>>>>>>> How about cutting the branch around mid-February and targeting
>>>>>>> to
>>>>>>>>>>>>>> release in a week or two after that.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Thejas
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
>> cws@apache.org
>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> I was wondering what people think about setting a tentative
>>>>>>> date
>>>>>>>>> for
>>>>>>>>>>> the
>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we agreed
>>>>>>> that
>>>>>>>>>> Hive
>>>>>>>>>>>>>>> should follow a time-based release model with new releases
>>>>>>> every
>>>>>>>>>> four
>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the next
>>>>>>> release
>>>>>>>>> in
>>>>>>>>>>>>>>> mid-February.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Carl
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>> http://mrunit.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>
>>>>
>>>> --
>>>> 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.
>>>
>>>
>>>
>>> --
>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>
>>
>> --
>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Thejas Nair <th...@hortonworks.com>.
I think we should include the following patches as well, they are in
patch available/review stage -
HIVE-5155 - (proxy user support for HS2) is patch available and has
undergone some reviews.
HIVE-6486 - Support secure Subject.doAs() in HiveServer2 JDBC client.
I have reviewed and +1'd it.
On Tue, Mar 4, 2014 at 12:13 PM, Thejas Nair <th...@hortonworks.com> wrote:
> I would like to include HIVE-5943/HIVE-5942 (describe role support ) and
> HIVE-6547 (metastore api - Role struct cleanup) in the release. I should
> have the patch for describe-role ready in a day or two, and for HIVE-6547 as
> well this week.
>
>
>
> On Tue, Mar 4, 2014 at 11:55 AM, Harish Butani <hb...@hortonworks.com>
> wrote:
>>
>> Yes sure. I am fine with porting over HIVE-5317 and dependents.
>> Besides, couldn't handle 104 angry fans (uh watchers) :)
>>
>> Let’s follow this procedure: if you have features that should go into
>> branch-0.13 please post a message here, give the community a chance to voice
>> their opinions.
>>
>> regards,
>> Harish.
>>
>>
>> On Mar 4, 2014, at 8:03 AM, Alan Gates <ga...@hortonworks.com> wrote:
>>
>> > Sure. I’d really like to get the work related to HIVE-5317 in 0.13.
>> > HIVE-5843 is patch available and hopefully can be checked in today. There
>> > are several more that depend on that one and can’t be made patch available
>> > until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t want
>> > to hold up the branching, but are you ok with those going in after the
>> > branch?
>> >
>> > Alan.
>> >
>> > On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com>
>> > wrote:
>> >
>> >> I plan to create the branch 5pm PST tomorrow.
>> >> Ok with everybody?
>> >>
>> >> regards,
>> >> Harish.
>> >>
>> >> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com>
>> >> wrote:
>> >>
>> >>> That's appropriate -- let the Hive release march forth on March 4th.
>> >>>
>> >>>
>> >>> -- Lefty
>> >>>
>> >>>
>> >>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani
>> >>> <hb...@hortonworks.com>wrote:
>> >>>
>> >>>> Ok,let’s set it for March 4th .
>> >>>>
>> >>>> regards,
>> >>>> Harish.
>> >>>>
>> >>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com>
>> >>>> wrote:
>> >>>>
>> >>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
>> >>>>> weekend time to get patches in.
>> >>>>>
>> >>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani
>> >>>>> <hb...@hortonworks.com>
>> >>>> wrote:
>> >>>>>> Yes makes sense.
>> >>>>>> How about we postpone the branching until 10am PST March 3rd, which
>> >>>>>> is
>> >>>> the following Monday.
>> >>>>>> Don’t see a point of setting the branch time to a Friday evening.
>> >>>>>> Do people agree?
>> >>>>>>
>> >>>>>> regards,
>> >>>>>> Harish.
>> >>>>>>
>> >>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>> +1
>> >>>>>>>
>> >>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair
>> >>>>>>> <th...@hortonworks.com>
>> >>>> wrote:
>> >>>>>>>> Can we wait for some few more days for the branching ? I have a
>> >>>>>>>> few
>> >>>> more
>> >>>>>>>> security fixes that I would like to get in, and we also have a
>> >>>>>>>> long
>> >>>>>>>> pre-commit queue ahead right now. How about branching around
>> >>>>>>>> Friday
>> >>>> next
>> >>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has
>> >>>>>>>> been
>> >>>>>>>> concluded, and we can get HIVE-6037 in as well.
>> >>>>>>>> -Thejas
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland
>> >>>>>>>> <br...@cloudera.com>
>> >>>> wrote:
>> >>>>>>>>
>> >>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
>> >>>> pending
>> >>>>>>>>> tests.
>> >>>>>>>>>
>> >>>>>>>>> Brock
>> >>>>>>>>>
>> >>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
>> >>>> wrote:
>> >>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
>> >>>> HiveConf.
>> >>>>>>>>> Could
>> >>>>>>>>>> it be included in this release? If it's not, I'll suspend
>> >>>>>>>>>> further
>> >>>>>>>>> rebasing
>> >>>>>>>>>> of it till next release (conflicts too frequently).
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz
>> >>>>>>>>>> <leftyleverenz@gmail.com
>> >>>>> :
>> >>>>>>>>>>
>> >>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0
>> >>>>>>>>>>> patches in
>> >>>> time
>> >>>>>>>>> for
>> >>>>>>>>>>> the release. It's a long and growing list, though, so no
>> >>>>>>>>>>> promises.
>> >>>>>>>>>>>
>> >>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
>> >>>> friendly
>> >>>>>>>>>>> in-house writer.
>> >>>>>>>>>>>
>> >>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
>> >>>> thejas@hortonworks.com>
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>>> Sounds good to me.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
>> >>>>>>>>> hbutani@hortonworks.com
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to
>> >>>>>>>>>>>>> cut a
>> >>>>>>>>> branch.
>> >>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
>> >>>>>>>>>>>>> The goal is to keep the release cycle short: couple of
>> >>>>>>>>>>>>> weeks; so
>> >>>>>>>>> after
>> >>>>>>>>>>>> the
>> >>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking
>> >>>>>>>>>>>>> in
>> >>>> only
>> >>>>>>>>>>>>> blocker/critical bug fixes.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> regards,
>> >>>>>>>>>>>>> Harish.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland
>> >>>>>>>>>>>>> <br...@cloudera.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Hi,
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
>> >>>>>>>>> commits to
>> >>>>>>>>>>>>> that
>> >>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Brock
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
>> >>>>>>>>>>>> hbutani@hortonworks.com
>> >>>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> Yes agree it is time to start planning for the next
>> >>>>>>>>>>>>>>> release.
>> >>>>>>>>>>>>>>> I would like to volunteer to do the release management
>> >>>>>>>>>>>>>>> duties
>> >>>> for
>> >>>>>>>>>>> this
>> >>>>>>>>>>>>>>> release(will be a great experience for me)
>> >>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with
>> >>>>>>>>>>>>>>> this.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> regards,
>> >>>>>>>>>>>>>>> Harish.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
>> >>>> thejas@hortonworks.com
>> >>>>>>>>>>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
>> >>>> release.
>> >>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted
>> >>>>>>>>>>>>>>>> patches
>> >>>>>>>>> that
>> >>>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
>> >>>> phase
>> >>>>>>>>> of
>> >>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
>> >>>>>>>>> laborious.
>> >>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to
>> >>>>>>>>>>>>>>>> get any
>> >>>>>>>>>>>> patches
>> >>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take
>> >>>>>>>>>>>>>>>> in
>> >>>>>>>>> only
>> >>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
>> >>>>>>>>>>>>>>>> How about cutting the branch around mid-February and
>> >>>>>>>>>>>>>>>> targeting
>> >>>>>>>>> to
>> >>>>>>>>>>>>>>>> release in a week or two after that.
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>>>> Thejas
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
>> >>>> cws@apache.org
>> >>>>>>>>>>
>> >>>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>>>>> I was wondering what people think about setting a
>> >>>>>>>>>>>>>>>>> tentative
>> >>>>>>>>> date
>> >>>>>>>>>>> for
>> >>>>>>>>>>>>> the
>> >>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we
>> >>>>>>>>>>>>>>>>> agreed
>> >>>>>>>>> that
>> >>>>>>>>>>>> Hive
>> >>>>>>>>>>>>>>>>> should follow a time-based release model with new
>> >>>>>>>>>>>>>>>>> releases
>> >>>>>>>>> every
>> >>>>>>>>>>>> four
>> >>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the
>> >>>>>>>>>>>>>>>>> next
>> >>>>>>>>> release
>> >>>>>>>>>>> in
>> >>>>>>>>>>>>>>>>> mid-February.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Thoughts?
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Thanks.
>> >>>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>>> Carl
>> >>>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>>>> 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.
>> >>>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> --
>> >>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>> >>>> http://mrunit.apache.org
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> --
>> >>>>>>>>>>>>> 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.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> --
>> >>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>> >>>>>>>>> http://mrunit.apache.org
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> 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.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> 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.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>> >>>>
>> >>>>
>> >>>> --
>> >>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Xuefu Zhang <xz...@cloudera.com>.
HIVE-6574 seems to be a blocker, and can we get this in 0.13?
Thanks,
Xuefu
On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hb...@hortonworks.com>wrote:
> ok sure.
> Tracking these with the JQL below. I don’t have permission to setup a
> Shared Filter; can someone help with this.
> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> resolved.
>
> regards,
> Harish.
>
> JQL:
>
> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687,
> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC,
> assignee
>
> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> pjayachandran@hortonworks.com> wrote:
>
> > Can you consider HIVE-6562 as well?
> >
> > HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> >
> > Thanks
> > Prasanth Jayachandran
> >
> > On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
> >
> >>
> >> Would like to get these in, if possible:
> >>
> >> HIVE-6012 restore backward compatibility of arithmetic operations
> >> HIVE-6434 Restrict function create/drop to admin roles
> >>
> >> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> >>
> >>> I have really big wish list(65 pending) but it would be time to focus
> on
> >>> finalization.
> >>>
> >>> - Small bugs
> >>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
> >>> HIVE-4790 MapredLocalTask task does not make virtual columns
> >>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> >>>
> >>> - Trivials
> >>> HIVE-6551 group by after join with skew join optimization references
> >>> invalid task sometimes
> >>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> >>> HIVE-6314 The logging (progress reporting) is too verbose
> >>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> >>> HIVE-5768 Beeline connection cannot be closed with !close command
> >>> HIVE-2752 Index names are case sensitive
> >>>
> >>> - Memory leakage
> >>> HIVE-6312 doAs with plain sasl auth should be session aware
> >>>
> >>> - Implementation is not accord with document
> >>> HIVE-6129 alter exchange is implemented in inverted manner
> >>>
> >>> I'll update the wiki, too.
> >>>
> >>>
> >>>
> >>>
> >>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
> >>>
> >>>> Tracking jiras to be applied to branch 0.13 here:
> >>>>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>
> >>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com>
> wrote:
> >>>>
> >>>>> the branch is created.
> >>>>> have changed the poms in both branches.
> >>>>> Planning to setup a wikipage to track jiras that will get ported to
> 0.13
> >>>>>
> >>>>> regards,
> >>>>> Harish.
> >>>>>
> >>>>>
> >>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
> >>>> wrote:
> >>>>>
> >>>>>> branching now. Will be changing the pom files on trunk.
> >>>>>> Will send another email when the branch and trunk changes are in.
> >>>>>>
> >>>>>>
> >>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>>> I have two patches still as patch-available, that have had +1s as
> >>>>>>> well, but are waiting on pre-commit tests picking them up go in to
> >>>>>>> 0.13:
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
> >>>>>>> property names from string constants to an enum in OrcFile)
> >>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where
> calls
> >>>>>>> like create table and drop table can fail if metastore-side
> >>>>>>> authorization is used in conjunction with custom
> >>>>>>> inputformat/outputformat/serdes that are not loadable from the
> >>>>>>> metastore-side)
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
just update the JQL.
On Mar 7, 2014, at 11:30 AM, Lefty Leverenz <le...@gmail.com> wrote:
> HIVE-6037 isn't on the list yet (synchronize HiveConf with
> hive-default.xml.template).
>
> What's the correct procedure for updating the
> wiki<https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status>,
> now that there's a JQL list as well as a table? Just add a row to the
> table and append the jira in the JQL list?
>
> -- Lefty
>
>
> On Fri, Mar 7, 2014 at 2:06 PM, Eugene Koifman <ek...@hortonworks.com>wrote:
>
>> HIVE-6576 please. w/o there is a backwards incompatible change in webhcat
>> REST api
>>
>>
>> On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org> wrote:
>>
>>> We should get 5567 and 5568 applied too. They are a bit stale, but I'll
>>> refresh them next week.
>>>
>>>
>>> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
>>>> wrote:
>>>
>>>> ok adding 6414, 6572, 6574 to the list
>>>> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
>>>>
>>>>> HIVE-6414 seems bad enough to included.
>>>>>
>>>>>
>>>>> On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
>>>
>>>> wrote:
>>>>>
>>>>>> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
>> patch
>>>>>> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
>> one
>>>>>> glaring bug on usage of mapred.min.split.size.per.rack and
>>>>>> mapred.min.split.size.per.node, and makes sure some of the other
>> conf
>>>>>> parameters we use are correctly through shims. I want this to go
>> into
>>>>>> 0.13 because I don't want a release of ours to go out with the
>>>>>> dual/old configs (and erroneous config in the per.rack/node case)
>> and
>>>>>> have that be expected behaviour to support in the future.
>>>>>>
>>>>>> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>> ok sure.
>>>>>>> Tracking these with the JQL below. I don’t have permission to
>> setup a
>>>>>> Shared Filter; can someone help with this.
>>>>>>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
>>>>>> resolved.
>>>>>>>
>>>>>>> regards,
>>>>>>> Harish.
>>>>>>>
>>>>>>> JQL:
>>>>>>>
>>>>>>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
>>>> HIVE-5687,
>>>>>> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
>>>>>> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
>>>>>> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
>>>>>> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
>>>>>> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
>> status
>>>> ASC,
>>>>>> assignee
>>>>>>>
>>>>>>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
>>>>>> pjayachandran@hortonworks.com> wrote:
>>>>>>>
>>>>>>>> Can you consider HIVE-6562 as well?
>>>>>>>>
>>>>>>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Prasanth Jayachandran
>>>>>>>>
>>>>>>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Would like to get these in, if possible:
>>>>>>>>>
>>>>>>>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>>>>>>>> HIVE-6434 Restrict function create/drop to admin roles
>>>>>>>>>
>>>>>>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have really big wish list(65 pending) but it would be time to
>>>> focus
>>>>>> on
>>>>>>>>>> finalization.
>>>>>>>>>>
>>>>>>>>>> - Small bugs
>>>>>>>>>> HIVE-6403 uncorrelated subquery is failing with
>>>> auto.convert.join=true
>>>>>>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>>>>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>>>>>>>
>>>>>>>>>> - Trivials
>>>>>>>>>> HIVE-6551 group by after join with skew join optimization
>>> references
>>>>>>>>>> invalid task sometimes
>>>>>>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>>>>>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>>>>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>>>>>>>> HIVE-5768 Beeline connection cannot be closed with !close
>> command
>>>>>>>>>> HIVE-2752 Index names are case sensitive
>>>>>>>>>>
>>>>>>>>>> - Memory leakage
>>>>>>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>>>>>>>
>>>>>>>>>> - Implementation is not accord with document
>>>>>>>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>>>>>>>
>>>>>>>>>> I'll update the wiki, too.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
>> hbutani@hortonworks.com
>>>> :
>>>>>>>>>>
>>>>>>>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>>>>>>>>
>>>>>>
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>>>>>>>
>>>>>>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> the branch is created.
>>>>>>>>>>>> have changed the poms in both branches.
>>>>>>>>>>>> Planning to setup a wikipage to track jiras that will get
>> ported
>>>> to
>>>>>> 0.13
>>>>>>>>>>>>
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Harish.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
>>>> hbutani@hortonworks.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>>>>>>>> Will send another email when the branch and trunk changes are
>>> in.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
>>> khorgath@gmail.com
>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have two patches still as patch-available, that have had
>> +1s
>>>> as
>>>>>>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
>>> in
>>>> to
>>>>>>>>>>>>>> 0.13:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
>> of
>>>>>> table
>>>>>>>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
>>>> where
>>>>>> calls
>>>>>>>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>>>>>>>> authorization is used in conjunction with custom
>>>>>>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
>> the
>>>>>>>>>>>>>> metastore-side)
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Lefty Leverenz <le...@gmail.com>.
>
> > Do we need to include HIVE-6037 in the release? I.e.: Is the current
> hive-default.xml.template very out of sync without it? It's a pretty large
> patch mostly aimed at making our lives easier, but doesn't impact the end
> user directly. Can we do that one trunk only?
Gunther, if HIVE-6037 were committed to trunk right away then Navis's
efforts wouldn't be lost so maybe we should consider doing that. But
recently I've been telling people not to bother updating
hive-default.xml.template because it's going to be generated from
HiveConf.java soon, so I'd have to figure out which parameters aren't in
the template file. That's less work than patching HiveConf.java with
recent config params after committing HIVE-6037, though.
I'm not the person who should make this decision. Let's hear from Navis,
Thejas, Brock, Prasanth, and anyone else who cares about this issue.
-- Lefty
On Fri, Mar 7, 2014 at 3:22 PM, Harish Butani <hb...@hortonworks.com>wrote:
> We should run tests on the branch. Given the number of patches going into
> the branch I propose for the next few days:
> - we trigger a run once a day. I can do this. In case of failures, we
> shouldn’t commit any more patches until the errors are resolved.
> (brock can you help with instructions on how to trigger a run on a
> branch)
>
> regards,
> Harish.
>
> On Mar 7, 2014, at 11:30 AM, Lefty Leverenz <le...@gmail.com>
> wrote:
>
> > HIVE-6037 isn't on the list yet (synchronize HiveConf with
> > hive-default.xml.template).
> >
> > What's the correct procedure for updating the
> > wiki<
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >,
> > now that there's a JQL list as well as a table? Just add a row to the
> > table and append the jira in the JQL list?
> >
> > -- Lefty
> >
> >
> > On Fri, Mar 7, 2014 at 2:06 PM, Eugene Koifman <ekoifman@hortonworks.com
> >wrote:
> >
> >> HIVE-6576 please. w/o there is a backwards incompatible change in
> webhcat
> >> REST api
> >>
> >>
> >> On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org>
> wrote:
> >>
> >>> We should get 5567 and 5568 applied too. They are a bit stale, but I'll
> >>> refresh them next week.
> >>>
> >>>
> >>> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <
> hbutani@hortonworks.com
> >>>> wrote:
> >>>
> >>>> ok adding 6414, 6572, 6574 to the list
> >>>> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> >>>>
> >>>>> HIVE-6414 seems bad enough to included.
> >>>>>
> >>>>>
> >>>>> On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
> >>>
> >>>> wrote:
> >>>>>
> >>>>>> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
> >> patch
> >>>>>> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
> >> one
> >>>>>> glaring bug on usage of mapred.min.split.size.per.rack and
> >>>>>> mapred.min.split.size.per.node, and makes sure some of the other
> >> conf
> >>>>>> parameters we use are correctly through shims. I want this to go
> >> into
> >>>>>> 0.13 because I don't want a release of ours to go out with the
> >>>>>> dual/old configs (and erroneous config in the per.rack/node case)
> >> and
> >>>>>> have that be expected behaviour to support in the future.
> >>>>>>
> >>>>>> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> >>> hbutani@hortonworks.com
> >>>>>
> >>>>>> wrote:
> >>>>>>> ok sure.
> >>>>>>> Tracking these with the JQL below. I don’t have permission to
> >> setup a
> >>>>>> Shared Filter; can someone help with this.
> >>>>>>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> >>>>>> resolved.
> >>>>>>>
> >>>>>>> regards,
> >>>>>>> Harish.
> >>>>>>>
> >>>>>>> JQL:
> >>>>>>>
> >>>>>>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> >>>> HIVE-5687,
> >>>>>> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> >>>>>> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> >>>>>> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> >>>>>> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> >>>>>> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
> >> status
> >>>> ASC,
> >>>>>> assignee
> >>>>>>>
> >>>>>>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> >>>>>> pjayachandran@hortonworks.com> wrote:
> >>>>>>>
> >>>>>>>> Can you consider HIVE-6562 as well?
> >>>>>>>>
> >>>>>>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>> Prasanth Jayachandran
> >>>>>>>>
> >>>>>>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> >>> wrote:
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Would like to get these in, if possible:
> >>>>>>>>>
> >>>>>>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> >>>>>>>>> HIVE-6434 Restrict function create/drop to admin roles
> >>>>>>>>>
> >>>>>>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> >>>>>>>>>
> >>>>>>>>>> I have really big wish list(65 pending) but it would be time to
> >>>> focus
> >>>>>> on
> >>>>>>>>>> finalization.
> >>>>>>>>>>
> >>>>>>>>>> - Small bugs
> >>>>>>>>>> HIVE-6403 uncorrelated subquery is failing with
> >>>> auto.convert.join=true
> >>>>>>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> >>>>>>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> >>>>>>>>>>
> >>>>>>>>>> - Trivials
> >>>>>>>>>> HIVE-6551 group by after join with skew join optimization
> >>> references
> >>>>>>>>>> invalid task sometimes
> >>>>>>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> >>>>>>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> >>>>>>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> >>>>>>>>>> HIVE-5768 Beeline connection cannot be closed with !close
> >> command
> >>>>>>>>>> HIVE-2752 Index names are case sensitive
> >>>>>>>>>>
> >>>>>>>>>> - Memory leakage
> >>>>>>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> >>>>>>>>>>
> >>>>>>>>>> - Implementation is not accord with document
> >>>>>>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> >>>>>>>>>>
> >>>>>>>>>> I'll update the wiki, too.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
> >> hbutani@hortonworks.com
> >>>> :
> >>>>>>>>>>
> >>>>>>>>>>> Tracking jiras to be applied to branch 0.13 here:
> >>>>>>>>>>>
> >>>>>>
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>>>>>>>>
> >>>>>>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> >>> hbutani@hortonworks.com
> >>>>>
> >>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> the branch is created.
> >>>>>>>>>>>> have changed the poms in both branches.
> >>>>>>>>>>>> Planning to setup a wikipage to track jiras that will get
> >> ported
> >>>> to
> >>>>>> 0.13
> >>>>>>>>>>>>
> >>>>>>>>>>>> regards,
> >>>>>>>>>>>> Harish.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> >>>> hbutani@hortonworks.com>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> branching now. Will be changing the pom files on trunk.
> >>>>>>>>>>>>> Will send another email when the branch and trunk changes are
> >>> in.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> >>> khorgath@gmail.com
> >>>>>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> I have two patches still as patch-available, that have had
> >> +1s
> >>>> as
> >>>>>>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
> >>> in
> >>>> to
> >>>>>>>>>>>>>> 0.13:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
> >> of
> >>>>>> table
> >>>>>>>>>>>>>> property names from string constants to an enum in OrcFile)
> >>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> >>>> where
> >>>>>> calls
> >>>>>>>>>>>>>> like create table and drop table can fail if metastore-side
> >>>>>>>>>>>>>> authorization is used in conjunction with custom
> >>>>>>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
> >> the
> >>>>>>>>>>>>>> metastore-side)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
We should run tests on the branch. Given the number of patches going into the branch I propose for the next few days:
- we trigger a run once a day. I can do this. In case of failures, we shouldn’t commit any more patches until the errors are resolved.
(brock can you help with instructions on how to trigger a run on a branch)
regards,
Harish.
On Mar 7, 2014, at 11:30 AM, Lefty Leverenz <le...@gmail.com> wrote:
> HIVE-6037 isn't on the list yet (synchronize HiveConf with
> hive-default.xml.template).
>
> What's the correct procedure for updating the
> wiki<https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status>,
> now that there's a JQL list as well as a table? Just add a row to the
> table and append the jira in the JQL list?
>
> -- Lefty
>
>
> On Fri, Mar 7, 2014 at 2:06 PM, Eugene Koifman <ek...@hortonworks.com>wrote:
>
>> HIVE-6576 please. w/o there is a backwards incompatible change in webhcat
>> REST api
>>
>>
>> On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org> wrote:
>>
>>> We should get 5567 and 5568 applied too. They are a bit stale, but I'll
>>> refresh them next week.
>>>
>>>
>>> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
>>>> wrote:
>>>
>>>> ok adding 6414, 6572, 6574 to the list
>>>> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
>>>>
>>>>> HIVE-6414 seems bad enough to included.
>>>>>
>>>>>
>>>>> On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
>>>
>>>> wrote:
>>>>>
>>>>>> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
>> patch
>>>>>> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
>> one
>>>>>> glaring bug on usage of mapred.min.split.size.per.rack and
>>>>>> mapred.min.split.size.per.node, and makes sure some of the other
>> conf
>>>>>> parameters we use are correctly through shims. I want this to go
>> into
>>>>>> 0.13 because I don't want a release of ours to go out with the
>>>>>> dual/old configs (and erroneous config in the per.rack/node case)
>> and
>>>>>> have that be expected behaviour to support in the future.
>>>>>>
>>>>>> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>> ok sure.
>>>>>>> Tracking these with the JQL below. I don’t have permission to
>> setup a
>>>>>> Shared Filter; can someone help with this.
>>>>>>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
>>>>>> resolved.
>>>>>>>
>>>>>>> regards,
>>>>>>> Harish.
>>>>>>>
>>>>>>> JQL:
>>>>>>>
>>>>>>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
>>>> HIVE-5687,
>>>>>> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
>>>>>> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
>>>>>> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
>>>>>> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
>>>>>> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
>> status
>>>> ASC,
>>>>>> assignee
>>>>>>>
>>>>>>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
>>>>>> pjayachandran@hortonworks.com> wrote:
>>>>>>>
>>>>>>>> Can you consider HIVE-6562 as well?
>>>>>>>>
>>>>>>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Prasanth Jayachandran
>>>>>>>>
>>>>>>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Would like to get these in, if possible:
>>>>>>>>>
>>>>>>>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>>>>>>>> HIVE-6434 Restrict function create/drop to admin roles
>>>>>>>>>
>>>>>>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have really big wish list(65 pending) but it would be time to
>>>> focus
>>>>>> on
>>>>>>>>>> finalization.
>>>>>>>>>>
>>>>>>>>>> - Small bugs
>>>>>>>>>> HIVE-6403 uncorrelated subquery is failing with
>>>> auto.convert.join=true
>>>>>>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>>>>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>>>>>>>
>>>>>>>>>> - Trivials
>>>>>>>>>> HIVE-6551 group by after join with skew join optimization
>>> references
>>>>>>>>>> invalid task sometimes
>>>>>>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>>>>>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>>>>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>>>>>>>> HIVE-5768 Beeline connection cannot be closed with !close
>> command
>>>>>>>>>> HIVE-2752 Index names are case sensitive
>>>>>>>>>>
>>>>>>>>>> - Memory leakage
>>>>>>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>>>>>>>
>>>>>>>>>> - Implementation is not accord with document
>>>>>>>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>>>>>>>
>>>>>>>>>> I'll update the wiki, too.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
>> hbutani@hortonworks.com
>>>> :
>>>>>>>>>>
>>>>>>>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>>>>>>>>
>>>>>>
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>>>>>>>
>>>>>>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> the branch is created.
>>>>>>>>>>>> have changed the poms in both branches.
>>>>>>>>>>>> Planning to setup a wikipage to track jiras that will get
>> ported
>>>> to
>>>>>> 0.13
>>>>>>>>>>>>
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Harish.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
>>>> hbutani@hortonworks.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>>>>>>>> Will send another email when the branch and trunk changes are
>>> in.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
>>> khorgath@gmail.com
>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have two patches still as patch-available, that have had
>> +1s
>>>> as
>>>>>>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
>>> in
>>>> to
>>>>>>>>>>>>>> 0.13:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
>> of
>>>>>> table
>>>>>>>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
>>>> where
>>>>>> calls
>>>>>>>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>>>>>>>> authorization is used in conjunction with custom
>>>>>>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
>> the
>>>>>>>>>>>>>> metastore-side)
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Gunther Hagleitner <gh...@hortonworks.com>.
Lefty,
Do we need to include HIVE-6037 in the release? I.e.: Is the current
hive-default.xml.template very out of sync without it? It's a pretty large
patch mostly aimed at making our lives easier, but doesn't impact the end
user directly. Can we do that one trunk only?
Thanks,
Gunther.
On Fri, Mar 7, 2014 at 11:30 AM, Lefty Leverenz <le...@gmail.com>wrote:
> HIVE-6037 isn't on the list yet (synchronize HiveConf with
> hive-default.xml.template).
>
> What's the correct procedure for updating the
> wiki<
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >,
> now that there's a JQL list as well as a table? Just add a row to the
> table and append the jira in the JQL list?
>
> -- Lefty
>
>
> On Fri, Mar 7, 2014 at 2:06 PM, Eugene Koifman <ekoifman@hortonworks.com
> >wrote:
>
> > HIVE-6576 please. w/o there is a backwards incompatible change in
> webhcat
> > REST api
> >
> >
> > On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org>
> wrote:
> >
> > > We should get 5567 and 5568 applied too. They are a bit stale, but I'll
> > > refresh them next week.
> > >
> > >
> > > On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <
> hbutani@hortonworks.com
> > > >wrote:
> > >
> > > > ok adding 6414, 6572, 6574 to the list
> > > > On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com>
> wrote:
> > > >
> > > > > HIVE-6414 seems bad enough to included.
> > > > >
> > > > >
> > > > > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <
> khorgath@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
> > patch
> > > > >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
> > one
> > > > >> glaring bug on usage of mapred.min.split.size.per.rack and
> > > > >> mapred.min.split.size.per.node, and makes sure some of the other
> > conf
> > > > >> parameters we use are correctly through shims. I want this to go
> > into
> > > > >> 0.13 because I don't want a release of ours to go out with the
> > > > >> dual/old configs (and erroneous config in the per.rack/node case)
> > and
> > > > >> have that be expected behaviour to support in the future.
> > > > >>
> > > > >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> > > hbutani@hortonworks.com
> > > > >
> > > > >> wrote:
> > > > >>> ok sure.
> > > > >>> Tracking these with the JQL below. I don’t have permission to
> > setup a
> > > > >> Shared Filter; can someone help with this.
> > > > >>> Of the 35 issues: 11 are still open, 22 are patch available, 2
> are
> > > > >> resolved.
> > > > >>>
> > > > >>> regards,
> > > > >>> Harish.
> > > > >>>
> > > > >>> JQL:
> > > > >>>
> > > > >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> > > > HIVE-5687,
> > > > >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> > > > >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> > > > >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> > > > >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> > > > >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
> > status
> > > > ASC,
> > > > >> assignee
> > > > >>>
> > > > >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> > > > >> pjayachandran@hortonworks.com> wrote:
> > > > >>>
> > > > >>>> Can you consider HIVE-6562 as well?
> > > > >>>>
> > > > >>>> HIVE-6562 - Protection from exceptions in ORC predicate
> evaluation
> > > > >>>>
> > > > >>>> Thanks
> > > > >>>> Prasanth Jayachandran
> > > > >>>>
> > > > >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> > > wrote:
> > > > >>>>
> > > > >>>>>
> > > > >>>>> Would like to get these in, if possible:
> > > > >>>>>
> > > > >>>>> HIVE-6012 restore backward compatibility of arithmetic
> operations
> > > > >>>>> HIVE-6434 Restrict function create/drop to admin roles
> > > > >>>>>
> > > > >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com>
> wrote:
> > > > >>>>>
> > > > >>>>>> I have really big wish list(65 pending) but it would be time
> to
> > > > focus
> > > > >> on
> > > > >>>>>> finalization.
> > > > >>>>>>
> > > > >>>>>> - Small bugs
> > > > >>>>>> HIVE-6403 uncorrelated subquery is failing with
> > > > auto.convert.join=true
> > > > >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> > > > >>>>>> HIVE-4293 Predicates following UDTF operator are removed by
> PPD
> > > > >>>>>>
> > > > >>>>>> - Trivials
> > > > >>>>>> HIVE-6551 group by after join with skew join optimization
> > > references
> > > > >>>>>> invalid task sometimes
> > > > >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> > > > >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> > > > >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> > > > >>>>>> HIVE-5768 Beeline connection cannot be closed with !close
> > command
> > > > >>>>>> HIVE-2752 Index names are case sensitive
> > > > >>>>>>
> > > > >>>>>> - Memory leakage
> > > > >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> > > > >>>>>>
> > > > >>>>>> - Implementation is not accord with document
> > > > >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> > > > >>>>>>
> > > > >>>>>> I'll update the wiki, too.
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
> > hbutani@hortonworks.com
> > > >:
> > > > >>>>>>
> > > > >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> > > > >>>>>>>
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> > > > >>>>>>>
> > > > >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> > > hbutani@hortonworks.com
> > > > >
> > > > >> wrote:
> > > > >>>>>>>
> > > > >>>>>>>> the branch is created.
> > > > >>>>>>>> have changed the poms in both branches.
> > > > >>>>>>>> Planning to setup a wikipage to track jiras that will get
> > ported
> > > > to
> > > > >> 0.13
> > > > >>>>>>>>
> > > > >>>>>>>> regards,
> > > > >>>>>>>> Harish.
> > > > >>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> > > > hbutani@hortonworks.com>
> > > > >>>>>>> wrote:
> > > > >>>>>>>>
> > > > >>>>>>>>> branching now. Will be changing the pom files on trunk.
> > > > >>>>>>>>> Will send another email when the branch and trunk changes
> are
> > > in.
> > > > >>>>>>>>>
> > > > >>>>>>>>>
> > > > >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> > > khorgath@gmail.com
> > > > >
> > > > >>>>>>> wrote:
> > > > >>>>>>>>>
> > > > >>>>>>>>>> I have two patches still as patch-available, that have had
> > +1s
> > > > as
> > > > >>>>>>>>>> well, but are waiting on pre-commit tests picking them up
> go
> > > in
> > > > to
> > > > >>>>>>>>>> 0.13:
> > > > >>>>>>>>>>
> > > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
> > of
> > > > >> table
> > > > >>>>>>>>>> property names from string constants to an enum in
> OrcFile)
> > > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes
> bug
> > > > where
> > > > >> calls
> > > > >>>>>>>>>> like create table and drop table can fail if
> metastore-side
> > > > >>>>>>>>>> authorization is used in conjunction with custom
> > > > >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
> > the
> > > > >>>>>>>>>> metastore-side)
> > > > >>>>>>>>>
> > > > >>>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> --
> > > > >>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Lefty Leverenz <le...@gmail.com>.
HIVE-6037 isn't on the list yet (synchronize HiveConf with
hive-default.xml.template).
What's the correct procedure for updating the
wiki<https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status>,
now that there's a JQL list as well as a table? Just add a row to the
table and append the jira in the JQL list?
-- Lefty
On Fri, Mar 7, 2014 at 2:06 PM, Eugene Koifman <ek...@hortonworks.com>wrote:
> HIVE-6576 please. w/o there is a backwards incompatible change in webhcat
> REST api
>
>
> On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org> wrote:
>
> > We should get 5567 and 5568 applied too. They are a bit stale, but I'll
> > refresh them next week.
> >
> >
> > On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
> > >wrote:
> >
> > > ok adding 6414, 6572, 6574 to the list
> > > On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> > >
> > > > HIVE-6414 seems bad enough to included.
> > > >
> > > >
> > > > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
> >
> > > wrote:
> > > >
> > > >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
> patch
> > > >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
> one
> > > >> glaring bug on usage of mapred.min.split.size.per.rack and
> > > >> mapred.min.split.size.per.node, and makes sure some of the other
> conf
> > > >> parameters we use are correctly through shims. I want this to go
> into
> > > >> 0.13 because I don't want a release of ours to go out with the
> > > >> dual/old configs (and erroneous config in the per.rack/node case)
> and
> > > >> have that be expected behaviour to support in the future.
> > > >>
> > > >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> > hbutani@hortonworks.com
> > > >
> > > >> wrote:
> > > >>> ok sure.
> > > >>> Tracking these with the JQL below. I don’t have permission to
> setup a
> > > >> Shared Filter; can someone help with this.
> > > >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> > > >> resolved.
> > > >>>
> > > >>> regards,
> > > >>> Harish.
> > > >>>
> > > >>> JQL:
> > > >>>
> > > >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> > > HIVE-5687,
> > > >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> > > >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> > > >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> > > >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> > > >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
> status
> > > ASC,
> > > >> assignee
> > > >>>
> > > >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> > > >> pjayachandran@hortonworks.com> wrote:
> > > >>>
> > > >>>> Can you consider HIVE-6562 as well?
> > > >>>>
> > > >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> > > >>>>
> > > >>>> Thanks
> > > >>>> Prasanth Jayachandran
> > > >>>>
> > > >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> > wrote:
> > > >>>>
> > > >>>>>
> > > >>>>> Would like to get these in, if possible:
> > > >>>>>
> > > >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> > > >>>>> HIVE-6434 Restrict function create/drop to admin roles
> > > >>>>>
> > > >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> > > >>>>>
> > > >>>>>> I have really big wish list(65 pending) but it would be time to
> > > focus
> > > >> on
> > > >>>>>> finalization.
> > > >>>>>>
> > > >>>>>> - Small bugs
> > > >>>>>> HIVE-6403 uncorrelated subquery is failing with
> > > auto.convert.join=true
> > > >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> > > >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> > > >>>>>>
> > > >>>>>> - Trivials
> > > >>>>>> HIVE-6551 group by after join with skew join optimization
> > references
> > > >>>>>> invalid task sometimes
> > > >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> > > >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> > > >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> > > >>>>>> HIVE-5768 Beeline connection cannot be closed with !close
> command
> > > >>>>>> HIVE-2752 Index names are case sensitive
> > > >>>>>>
> > > >>>>>> - Memory leakage
> > > >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> > > >>>>>>
> > > >>>>>> - Implementation is not accord with document
> > > >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> > > >>>>>>
> > > >>>>>> I'll update the wiki, too.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
> hbutani@hortonworks.com
> > >:
> > > >>>>>>
> > > >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> > > >>>>>>>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> > > >>>>>>>
> > > >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> > hbutani@hortonworks.com
> > > >
> > > >> wrote:
> > > >>>>>>>
> > > >>>>>>>> the branch is created.
> > > >>>>>>>> have changed the poms in both branches.
> > > >>>>>>>> Planning to setup a wikipage to track jiras that will get
> ported
> > > to
> > > >> 0.13
> > > >>>>>>>>
> > > >>>>>>>> regards,
> > > >>>>>>>> Harish.
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> > > hbutani@hortonworks.com>
> > > >>>>>>> wrote:
> > > >>>>>>>>
> > > >>>>>>>>> branching now. Will be changing the pom files on trunk.
> > > >>>>>>>>> Will send another email when the branch and trunk changes are
> > in.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> > khorgath@gmail.com
> > > >
> > > >>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> I have two patches still as patch-available, that have had
> +1s
> > > as
> > > >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
> > in
> > > to
> > > >>>>>>>>>> 0.13:
> > > >>>>>>>>>>
> > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
> of
> > > >> table
> > > >>>>>>>>>> property names from string constants to an enum in OrcFile)
> > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> > > where
> > > >> calls
> > > >>>>>>>>>> like create table and drop table can fail if metastore-side
> > > >>>>>>>>>> authorization is used in conjunction with custom
> > > >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
> the
> > > >>>>>>>>>> metastore-side)
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Eugene Koifman <ek...@hortonworks.com>.
HIVE-6576 please. w/o there is a backwards incompatible change in webhcat
REST api
On Fri, Mar 7, 2014 at 10:45 AM, Owen O'Malley <om...@apache.org> wrote:
> We should get 5567 and 5568 applied too. They are a bit stale, but I'll
> refresh them next week.
>
>
> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
> >wrote:
>
> > ok adding 6414, 6572, 6574 to the list
> > On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> >
> > > HIVE-6414 seems bad enough to included.
> > >
> > >
> > > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com>
> > wrote:
> > >
> > >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> > >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> > >> glaring bug on usage of mapred.min.split.size.per.rack and
> > >> mapred.min.split.size.per.node, and makes sure some of the other conf
> > >> parameters we use are correctly through shims. I want this to go into
> > >> 0.13 because I don't want a release of ours to go out with the
> > >> dual/old configs (and erroneous config in the per.rack/node case) and
> > >> have that be expected behaviour to support in the future.
> > >>
> > >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> hbutani@hortonworks.com
> > >
> > >> wrote:
> > >>> ok sure.
> > >>> Tracking these with the JQL below. I don’t have permission to setup a
> > >> Shared Filter; can someone help with this.
> > >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> > >> resolved.
> > >>>
> > >>> regards,
> > >>> Harish.
> > >>>
> > >>> JQL:
> > >>>
> > >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> > HIVE-5687,
> > >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> > >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> > >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> > >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> > >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status
> > ASC,
> > >> assignee
> > >>>
> > >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> > >> pjayachandran@hortonworks.com> wrote:
> > >>>
> > >>>> Can you consider HIVE-6562 as well?
> > >>>>
> > >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> > >>>>
> > >>>> Thanks
> > >>>> Prasanth Jayachandran
> > >>>>
> > >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> wrote:
> > >>>>
> > >>>>>
> > >>>>> Would like to get these in, if possible:
> > >>>>>
> > >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> > >>>>> HIVE-6434 Restrict function create/drop to admin roles
> > >>>>>
> > >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> > >>>>>
> > >>>>>> I have really big wish list(65 pending) but it would be time to
> > focus
> > >> on
> > >>>>>> finalization.
> > >>>>>>
> > >>>>>> - Small bugs
> > >>>>>> HIVE-6403 uncorrelated subquery is failing with
> > auto.convert.join=true
> > >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> > >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> > >>>>>>
> > >>>>>> - Trivials
> > >>>>>> HIVE-6551 group by after join with skew join optimization
> references
> > >>>>>> invalid task sometimes
> > >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> > >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> > >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> > >>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
> > >>>>>> HIVE-2752 Index names are case sensitive
> > >>>>>>
> > >>>>>> - Memory leakage
> > >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> > >>>>>>
> > >>>>>> - Implementation is not accord with document
> > >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> > >>>>>>
> > >>>>>> I'll update the wiki, too.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hbutani@hortonworks.com
> >:
> > >>>>>>
> > >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> > >>>>>>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> > >>>>>>>
> > >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> hbutani@hortonworks.com
> > >
> > >> wrote:
> > >>>>>>>
> > >>>>>>>> the branch is created.
> > >>>>>>>> have changed the poms in both branches.
> > >>>>>>>> Planning to setup a wikipage to track jiras that will get ported
> > to
> > >> 0.13
> > >>>>>>>>
> > >>>>>>>> regards,
> > >>>>>>>> Harish.
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> > hbutani@hortonworks.com>
> > >>>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>>> branching now. Will be changing the pom files on trunk.
> > >>>>>>>>> Will send another email when the branch and trunk changes are
> in.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> khorgath@gmail.com
> > >
> > >>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> I have two patches still as patch-available, that have had +1s
> > as
> > >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
> in
> > to
> > >>>>>>>>>> 0.13:
> > >>>>>>>>>>
> > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
> > >> table
> > >>>>>>>>>> property names from string constants to an enum in OrcFile)
> > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> > where
> > >> calls
> > >>>>>>>>>> like create table and drop table can fail if metastore-side
> > >>>>>>>>>> authorization is used in conjunction with custom
> > >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
> > >>>>>>>>>> metastore-side)
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Owen O'Malley <om...@apache.org>.
We should get 5567 and 5568 applied too. They are a bit stale, but I'll
refresh them next week.
On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hb...@hortonworks.com>wrote:
> ok adding 6414, 6572, 6574 to the list
> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
>
> > HIVE-6414 seems bad enough to included.
> >
> >
> > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com>
> wrote:
> >
> >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> >> glaring bug on usage of mapred.min.split.size.per.rack and
> >> mapred.min.split.size.per.node, and makes sure some of the other conf
> >> parameters we use are correctly through shims. I want this to go into
> >> 0.13 because I don't want a release of ours to go out with the
> >> dual/old configs (and erroneous config in the per.rack/node case) and
> >> have that be expected behaviour to support in the future.
> >>
> >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hbutani@hortonworks.com
> >
> >> wrote:
> >>> ok sure.
> >>> Tracking these with the JQL below. I don’t have permission to setup a
> >> Shared Filter; can someone help with this.
> >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> >> resolved.
> >>>
> >>> regards,
> >>> Harish.
> >>>
> >>> JQL:
> >>>
> >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> HIVE-5687,
> >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status
> ASC,
> >> assignee
> >>>
> >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> >> pjayachandran@hortonworks.com> wrote:
> >>>
> >>>> Can you consider HIVE-6562 as well?
> >>>>
> >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> >>>>
> >>>> Thanks
> >>>> Prasanth Jayachandran
> >>>>
> >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
> >>>>
> >>>>>
> >>>>> Would like to get these in, if possible:
> >>>>>
> >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> >>>>> HIVE-6434 Restrict function create/drop to admin roles
> >>>>>
> >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> >>>>>
> >>>>>> I have really big wish list(65 pending) but it would be time to
> focus
> >> on
> >>>>>> finalization.
> >>>>>>
> >>>>>> - Small bugs
> >>>>>> HIVE-6403 uncorrelated subquery is failing with
> auto.convert.join=true
> >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> >>>>>>
> >>>>>> - Trivials
> >>>>>> HIVE-6551 group by after join with skew join optimization references
> >>>>>> invalid task sometimes
> >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> >>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
> >>>>>> HIVE-2752 Index names are case sensitive
> >>>>>>
> >>>>>> - Memory leakage
> >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> >>>>>>
> >>>>>> - Implementation is not accord with document
> >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> >>>>>>
> >>>>>> I'll update the wiki, too.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
> >>>>>>
> >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> >>>>>>>
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>>>>
> >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hbutani@hortonworks.com
> >
> >> wrote:
> >>>>>>>
> >>>>>>>> the branch is created.
> >>>>>>>> have changed the poms in both branches.
> >>>>>>>> Planning to setup a wikipage to track jiras that will get ported
> to
> >> 0.13
> >>>>>>>>
> >>>>>>>> regards,
> >>>>>>>> Harish.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> hbutani@hortonworks.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> branching now. Will be changing the pom files on trunk.
> >>>>>>>>> Will send another email when the branch and trunk changes are in.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <khorgath@gmail.com
> >
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> I have two patches still as patch-available, that have had +1s
> as
> >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go in
> to
> >>>>>>>>>> 0.13:
> >>>>>>>>>>
> >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
> >> table
> >>>>>>>>>> property names from string constants to an enum in OrcFile)
> >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> where
> >> calls
> >>>>>>>>>> like create table and drop table can fail if metastore-side
> >>>>>>>>>> authorization is used in conjunction with custom
> >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
> >>>>>>>>>> metastore-side)
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
Szehon and Brock. Thank you!
regards,
Harish.
On Mar 10, 2014, at 1:07 PM, Szehon Ho <sz...@cloudera.com> wrote:
> Hi all,
>
> As per Harish request, I have set up builds on the PTest Infra to test 0.13
> release branch for faster turnaround. Adding location as FYI:
>
> http://bigtop01.cloudera.org:8080/view/Hive/job/Hive-0.13-hadoop1/
> http://bigtop01.cloudera.org:8080/view/Hive/job/Hive-0.13-hadoop2/
>
> It will run nightly at different times than the trunk ones and also
> on-demand. It is running the first trial run now.
>
> Thanks
> Szehon
>
>
> On Sat, Mar 8, 2014 at 8:28 PM, Harish Butani <hb...@hortonworks.com>wrote:
>
>> i added it.
>>
>>
>> On Sat, Mar 8, 2014 at 5:30 PM, Xuefu Zhang <xz...@cloudera.com> wrote:
>>
>>> Hi Harish,
>>>
>>>
>>> 6414 seem missing from:
>>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status.
>>>
>>> Thanks,
>>> Xuefu
>>>
>>>
>>> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
>>>> wrote:
>>>
>>>> ok adding 6414, 6572, 6574 to the list
>>>> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
>>>>
>>>>> HIVE-6414 seems bad enough to included.
>>>>>
>>>>>
>>>>> On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
>>>
>>>> wrote:
>>>>>
>>>>>> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
>> patch
>>>>>> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
>> one
>>>>>> glaring bug on usage of mapred.min.split.size.per.rack and
>>>>>> mapred.min.split.size.per.node, and makes sure some of the other
>> conf
>>>>>> parameters we use are correctly through shims. I want this to go
>> into
>>>>>> 0.13 because I don't want a release of ours to go out with the
>>>>>> dual/old configs (and erroneous config in the per.rack/node case)
>> and
>>>>>> have that be expected behaviour to support in the future.
>>>>>>
>>>>>> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>> ok sure.
>>>>>>> Tracking these with the JQL below. I don’t have permission to
>> setup a
>>>>>> Shared Filter; can someone help with this.
>>>>>>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
>>>>>> resolved.
>>>>>>>
>>>>>>> regards,
>>>>>>> Harish.
>>>>>>>
>>>>>>> JQL:
>>>>>>>
>>>>>>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
>>>> HIVE-5687,
>>>>>> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
>>>>>> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
>>>>>> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
>>>>>> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
>>>>>> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
>> status
>>>> ASC,
>>>>>> assignee
>>>>>>>
>>>>>>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
>>>>>> pjayachandran@hortonworks.com> wrote:
>>>>>>>
>>>>>>>> Can you consider HIVE-6562 as well?
>>>>>>>>
>>>>>>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Prasanth Jayachandran
>>>>>>>>
>>>>>>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Would like to get these in, if possible:
>>>>>>>>>
>>>>>>>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>>>>>>>> HIVE-6434 Restrict function create/drop to admin roles
>>>>>>>>>
>>>>>>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>>>>>>>
>>>>>>>>>> I have really big wish list(65 pending) but it would be time to
>>>> focus
>>>>>> on
>>>>>>>>>> finalization.
>>>>>>>>>>
>>>>>>>>>> - Small bugs
>>>>>>>>>> HIVE-6403 uncorrelated subquery is failing with
>>>> auto.convert.join=true
>>>>>>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>>>>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>>>>>>>
>>>>>>>>>> - Trivials
>>>>>>>>>> HIVE-6551 group by after join with skew join optimization
>>> references
>>>>>>>>>> invalid task sometimes
>>>>>>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>>>>>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>>>>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>>>>>>>> HIVE-5768 Beeline connection cannot be closed with !close
>> command
>>>>>>>>>> HIVE-2752 Index names are case sensitive
>>>>>>>>>>
>>>>>>>>>> - Memory leakage
>>>>>>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>>>>>>>
>>>>>>>>>> - Implementation is not accord with document
>>>>>>>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>>>>>>>
>>>>>>>>>> I'll update the wiki, too.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
>> hbutani@hortonworks.com
>>>> :
>>>>>>>>>>
>>>>>>>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>>>>>>>>
>>>>>>
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>>>>>>>
>>>>>>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
>>> hbutani@hortonworks.com
>>>>>
>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> the branch is created.
>>>>>>>>>>>> have changed the poms in both branches.
>>>>>>>>>>>> Planning to setup a wikipage to track jiras that will get
>> ported
>>>> to
>>>>>> 0.13
>>>>>>>>>>>>
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Harish.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
>>>> hbutani@hortonworks.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>>>>>>>> Will send another email when the branch and trunk changes are
>>> in.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
>>> khorgath@gmail.com
>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have two patches still as patch-available, that have had
>> +1s
>>>> as
>>>>>>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
>>> in
>>>> to
>>>>>>>>>>>>>> 0.13:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
>> of
>>>>>> table
>>>>>>>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
>>>> where
>>>>>> calls
>>>>>>>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>>>>>>>> authorization is used in conjunction with custom
>>>>>>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
>> the
>>>>>>>>>>>>>> metastore-side)
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Szehon Ho <sz...@cloudera.com>.
Hi all,
As per Harish request, I have set up builds on the PTest Infra to test 0.13
release branch for faster turnaround. Adding location as FYI:
http://bigtop01.cloudera.org:8080/view/Hive/job/Hive-0.13-hadoop1/
http://bigtop01.cloudera.org:8080/view/Hive/job/Hive-0.13-hadoop2/
It will run nightly at different times than the trunk ones and also
on-demand. It is running the first trial run now.
Thanks
Szehon
On Sat, Mar 8, 2014 at 8:28 PM, Harish Butani <hb...@hortonworks.com>wrote:
> i added it.
>
>
> On Sat, Mar 8, 2014 at 5:30 PM, Xuefu Zhang <xz...@cloudera.com> wrote:
>
> > Hi Harish,
> >
> >
> > 6414 seem missing from:
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status.
> >
> > Thanks,
> > Xuefu
> >
> >
> > On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
> > >wrote:
> >
> > > ok adding 6414, 6572, 6574 to the list
> > > On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> > >
> > > > HIVE-6414 seems bad enough to included.
> > > >
> > > >
> > > > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <khorgath@gmail.com
> >
> > > wrote:
> > > >
> > > >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a
> patch
> > > >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes
> one
> > > >> glaring bug on usage of mapred.min.split.size.per.rack and
> > > >> mapred.min.split.size.per.node, and makes sure some of the other
> conf
> > > >> parameters we use are correctly through shims. I want this to go
> into
> > > >> 0.13 because I don't want a release of ours to go out with the
> > > >> dual/old configs (and erroneous config in the per.rack/node case)
> and
> > > >> have that be expected behaviour to support in the future.
> > > >>
> > > >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> > hbutani@hortonworks.com
> > > >
> > > >> wrote:
> > > >>> ok sure.
> > > >>> Tracking these with the JQL below. I don’t have permission to
> setup a
> > > >> Shared Filter; can someone help with this.
> > > >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> > > >> resolved.
> > > >>>
> > > >>> regards,
> > > >>> Harish.
> > > >>>
> > > >>> JQL:
> > > >>>
> > > >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> > > HIVE-5687,
> > > >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> > > >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> > > >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> > > >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> > > >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY
> status
> > > ASC,
> > > >> assignee
> > > >>>
> > > >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> > > >> pjayachandran@hortonworks.com> wrote:
> > > >>>
> > > >>>> Can you consider HIVE-6562 as well?
> > > >>>>
> > > >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> > > >>>>
> > > >>>> Thanks
> > > >>>> Prasanth Jayachandran
> > > >>>>
> > > >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> > wrote:
> > > >>>>
> > > >>>>>
> > > >>>>> Would like to get these in, if possible:
> > > >>>>>
> > > >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> > > >>>>> HIVE-6434 Restrict function create/drop to admin roles
> > > >>>>>
> > > >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> > > >>>>>
> > > >>>>>> I have really big wish list(65 pending) but it would be time to
> > > focus
> > > >> on
> > > >>>>>> finalization.
> > > >>>>>>
> > > >>>>>> - Small bugs
> > > >>>>>> HIVE-6403 uncorrelated subquery is failing with
> > > auto.convert.join=true
> > > >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> > > >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> > > >>>>>>
> > > >>>>>> - Trivials
> > > >>>>>> HIVE-6551 group by after join with skew join optimization
> > references
> > > >>>>>> invalid task sometimes
> > > >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> > > >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> > > >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> > > >>>>>> HIVE-5768 Beeline connection cannot be closed with !close
> command
> > > >>>>>> HIVE-2752 Index names are case sensitive
> > > >>>>>>
> > > >>>>>> - Memory leakage
> > > >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> > > >>>>>>
> > > >>>>>> - Implementation is not accord with document
> > > >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> > > >>>>>>
> > > >>>>>> I'll update the wiki, too.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <
> hbutani@hortonworks.com
> > >:
> > > >>>>>>
> > > >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> > > >>>>>>>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> > > >>>>>>>
> > > >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> > hbutani@hortonworks.com
> > > >
> > > >> wrote:
> > > >>>>>>>
> > > >>>>>>>> the branch is created.
> > > >>>>>>>> have changed the poms in both branches.
> > > >>>>>>>> Planning to setup a wikipage to track jiras that will get
> ported
> > > to
> > > >> 0.13
> > > >>>>>>>>
> > > >>>>>>>> regards,
> > > >>>>>>>> Harish.
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> > > hbutani@hortonworks.com>
> > > >>>>>>> wrote:
> > > >>>>>>>>
> > > >>>>>>>>> branching now. Will be changing the pom files on trunk.
> > > >>>>>>>>> Will send another email when the branch and trunk changes are
> > in.
> > > >>>>>>>>>
> > > >>>>>>>>>
> > > >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> > khorgath@gmail.com
> > > >
> > > >>>>>>> wrote:
> > > >>>>>>>>>
> > > >>>>>>>>>> I have two patches still as patch-available, that have had
> +1s
> > > as
> > > >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
> > in
> > > to
> > > >>>>>>>>>> 0.13:
> > > >>>>>>>>>>
> > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor
> of
> > > >> table
> > > >>>>>>>>>> property names from string constants to an enum in OrcFile)
> > > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> > > where
> > > >> calls
> > > >>>>>>>>>> like create table and drop table can fail if metastore-side
> > > >>>>>>>>>> authorization is used in conjunction with custom
> > > >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from
> the
> > > >>>>>>>>>> metastore-side)
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> --
> > > >>>>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
i added it.
On Sat, Mar 8, 2014 at 5:30 PM, Xuefu Zhang <xz...@cloudera.com> wrote:
> Hi Harish,
>
>
> 6414 seem missing from:
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status.
>
> Thanks,
> Xuefu
>
>
> On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hbutani@hortonworks.com
> >wrote:
>
> > ok adding 6414, 6572, 6574 to the list
> > On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> >
> > > HIVE-6414 seems bad enough to included.
> > >
> > >
> > > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com>
> > wrote:
> > >
> > >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> > >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> > >> glaring bug on usage of mapred.min.split.size.per.rack and
> > >> mapred.min.split.size.per.node, and makes sure some of the other conf
> > >> parameters we use are correctly through shims. I want this to go into
> > >> 0.13 because I don't want a release of ours to go out with the
> > >> dual/old configs (and erroneous config in the per.rack/node case) and
> > >> have that be expected behaviour to support in the future.
> > >>
> > >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <
> hbutani@hortonworks.com
> > >
> > >> wrote:
> > >>> ok sure.
> > >>> Tracking these with the JQL below. I don’t have permission to setup a
> > >> Shared Filter; can someone help with this.
> > >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> > >> resolved.
> > >>>
> > >>> regards,
> > >>> Harish.
> > >>>
> > >>> JQL:
> > >>>
> > >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> > HIVE-5687,
> > >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> > >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> > >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> > >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> > >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status
> > ASC,
> > >> assignee
> > >>>
> > >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> > >> pjayachandran@hortonworks.com> wrote:
> > >>>
> > >>>> Can you consider HIVE-6562 as well?
> > >>>>
> > >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> > >>>>
> > >>>> Thanks
> > >>>> Prasanth Jayachandran
> > >>>>
> > >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com>
> wrote:
> > >>>>
> > >>>>>
> > >>>>> Would like to get these in, if possible:
> > >>>>>
> > >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> > >>>>> HIVE-6434 Restrict function create/drop to admin roles
> > >>>>>
> > >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> > >>>>>
> > >>>>>> I have really big wish list(65 pending) but it would be time to
> > focus
> > >> on
> > >>>>>> finalization.
> > >>>>>>
> > >>>>>> - Small bugs
> > >>>>>> HIVE-6403 uncorrelated subquery is failing with
> > auto.convert.join=true
> > >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> > >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> > >>>>>>
> > >>>>>> - Trivials
> > >>>>>> HIVE-6551 group by after join with skew join optimization
> references
> > >>>>>> invalid task sometimes
> > >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> > >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> > >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> > >>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
> > >>>>>> HIVE-2752 Index names are case sensitive
> > >>>>>>
> > >>>>>> - Memory leakage
> > >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> > >>>>>>
> > >>>>>> - Implementation is not accord with document
> > >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> > >>>>>>
> > >>>>>> I'll update the wiki, too.
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hbutani@hortonworks.com
> >:
> > >>>>>>
> > >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> > >>>>>>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> > >>>>>>>
> > >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <
> hbutani@hortonworks.com
> > >
> > >> wrote:
> > >>>>>>>
> > >>>>>>>> the branch is created.
> > >>>>>>>> have changed the poms in both branches.
> > >>>>>>>> Planning to setup a wikipage to track jiras that will get ported
> > to
> > >> 0.13
> > >>>>>>>>
> > >>>>>>>> regards,
> > >>>>>>>> Harish.
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> > hbutani@hortonworks.com>
> > >>>>>>> wrote:
> > >>>>>>>>
> > >>>>>>>>> branching now. Will be changing the pom files on trunk.
> > >>>>>>>>> Will send another email when the branch and trunk changes are
> in.
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <
> khorgath@gmail.com
> > >
> > >>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> I have two patches still as patch-available, that have had +1s
> > as
> > >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go
> in
> > to
> > >>>>>>>>>> 0.13:
> > >>>>>>>>>>
> > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
> > >> table
> > >>>>>>>>>> property names from string constants to an enum in OrcFile)
> > >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> > where
> > >> calls
> > >>>>>>>>>> like create table and drop table can fail if metastore-side
> > >>>>>>>>>> authorization is used in conjunction with custom
> > >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
> > >>>>>>>>>> metastore-side)
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> --
> > >>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Xuefu Zhang <xz...@cloudera.com>.
Hi Harish,
6414 seem missing from:
https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status.
Thanks,
Xuefu
On Fri, Mar 7, 2014 at 10:41 AM, Harish Butani <hb...@hortonworks.com>wrote:
> ok adding 6414, 6572, 6574 to the list
> On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
>
> > HIVE-6414 seems bad enough to included.
> >
> >
> > On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com>
> wrote:
> >
> >> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> >> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> >> glaring bug on usage of mapred.min.split.size.per.rack and
> >> mapred.min.split.size.per.node, and makes sure some of the other conf
> >> parameters we use are correctly through shims. I want this to go into
> >> 0.13 because I don't want a release of ours to go out with the
> >> dual/old configs (and erroneous config in the per.rack/node case) and
> >> have that be expected behaviour to support in the future.
> >>
> >> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hbutani@hortonworks.com
> >
> >> wrote:
> >>> ok sure.
> >>> Tracking these with the JQL below. I don’t have permission to setup a
> >> Shared Filter; can someone help with this.
> >>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> >> resolved.
> >>>
> >>> regards,
> >>> Harish.
> >>>
> >>> JQL:
> >>>
> >>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460,
> HIVE-5687,
> >> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> >> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> >> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> >> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> >> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status
> ASC,
> >> assignee
> >>>
> >>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> >> pjayachandran@hortonworks.com> wrote:
> >>>
> >>>> Can you consider HIVE-6562 as well?
> >>>>
> >>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> >>>>
> >>>> Thanks
> >>>> Prasanth Jayachandran
> >>>>
> >>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
> >>>>
> >>>>>
> >>>>> Would like to get these in, if possible:
> >>>>>
> >>>>> HIVE-6012 restore backward compatibility of arithmetic operations
> >>>>> HIVE-6434 Restrict function create/drop to admin roles
> >>>>>
> >>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> >>>>>
> >>>>>> I have really big wish list(65 pending) but it would be time to
> focus
> >> on
> >>>>>> finalization.
> >>>>>>
> >>>>>> - Small bugs
> >>>>>> HIVE-6403 uncorrelated subquery is failing with
> auto.convert.join=true
> >>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> >>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> >>>>>>
> >>>>>> - Trivials
> >>>>>> HIVE-6551 group by after join with skew join optimization references
> >>>>>> invalid task sometimes
> >>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> >>>>>> HIVE-6314 The logging (progress reporting) is too verbose
> >>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> >>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
> >>>>>> HIVE-2752 Index names are case sensitive
> >>>>>>
> >>>>>> - Memory leakage
> >>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
> >>>>>>
> >>>>>> - Implementation is not accord with document
> >>>>>> HIVE-6129 alter exchange is implemented in inverted manner
> >>>>>>
> >>>>>> I'll update the wiki, too.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
> >>>>>>
> >>>>>>> Tracking jiras to be applied to branch 0.13 here:
> >>>>>>>
> >>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>>>>
> >>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hbutani@hortonworks.com
> >
> >> wrote:
> >>>>>>>
> >>>>>>>> the branch is created.
> >>>>>>>> have changed the poms in both branches.
> >>>>>>>> Planning to setup a wikipage to track jiras that will get ported
> to
> >> 0.13
> >>>>>>>>
> >>>>>>>> regards,
> >>>>>>>> Harish.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <
> hbutani@hortonworks.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> branching now. Will be changing the pom files on trunk.
> >>>>>>>>> Will send another email when the branch and trunk changes are in.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <khorgath@gmail.com
> >
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> I have two patches still as patch-available, that have had +1s
> as
> >>>>>>>>>> well, but are waiting on pre-commit tests picking them up go in
> to
> >>>>>>>>>> 0.13:
> >>>>>>>>>>
> >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
> >> table
> >>>>>>>>>> property names from string constants to an enum in OrcFile)
> >>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug
> where
> >> calls
> >>>>>>>>>> like create table and drop table can fail if metastore-side
> >>>>>>>>>> authorization is used in conjunction with custom
> >>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
> >>>>>>>>>> metastore-side)
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
ok adding 6414, 6572, 6574 to the list
On Mar 7, 2014, at 10:27 AM, Xuefu Zhang <xz...@cloudera.com> wrote:
> HIVE-6414 seems bad enough to included.
>
>
> On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
>
>> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
>> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
>> glaring bug on usage of mapred.min.split.size.per.rack and
>> mapred.min.split.size.per.node, and makes sure some of the other conf
>> parameters we use are correctly through shims. I want this to go into
>> 0.13 because I don't want a release of ours to go out with the
>> dual/old configs (and erroneous config in the per.rack/node case) and
>> have that be expected behaviour to support in the future.
>>
>> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hb...@hortonworks.com>
>> wrote:
>>> ok sure.
>>> Tracking these with the JQL below. I don’t have permission to setup a
>> Shared Filter; can someone help with this.
>>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are
>> resolved.
>>>
>>> regards,
>>> Harish.
>>>
>>> JQL:
>>>
>>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687,
>> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
>> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
>> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
>> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
>> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC,
>> assignee
>>>
>>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
>> pjayachandran@hortonworks.com> wrote:
>>>
>>>> Can you consider HIVE-6562 as well?
>>>>
>>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>>>
>>>> Thanks
>>>> Prasanth Jayachandran
>>>>
>>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
>>>>
>>>>>
>>>>> Would like to get these in, if possible:
>>>>>
>>>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>>>> HIVE-6434 Restrict function create/drop to admin roles
>>>>>
>>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>>>
>>>>>> I have really big wish list(65 pending) but it would be time to focus
>> on
>>>>>> finalization.
>>>>>>
>>>>>> - Small bugs
>>>>>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
>>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>>>
>>>>>> - Trivials
>>>>>> HIVE-6551 group by after join with skew join optimization references
>>>>>> invalid task sometimes
>>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
>>>>>> HIVE-2752 Index names are case sensitive
>>>>>>
>>>>>> - Memory leakage
>>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>>>
>>>>>> - Implementation is not accord with document
>>>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>>>
>>>>>> I'll update the wiki, too.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>>>>>>
>>>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>>>>
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>>>
>>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com>
>> wrote:
>>>>>>>
>>>>>>>> the branch is created.
>>>>>>>> have changed the poms in both branches.
>>>>>>>> Planning to setup a wikipage to track jiras that will get ported to
>> 0.13
>>>>>>>>
>>>>>>>> regards,
>>>>>>>> Harish.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>>>> Will send another email when the branch and trunk changes are in.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> I have two patches still as patch-available, that have had +1s as
>>>>>>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>>>>>>> 0.13:
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
>> table
>>>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where
>> calls
>>>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>>>> authorization is used in conjunction with custom
>>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>>>>>>> metastore-side)
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Xuefu Zhang <xz...@cloudera.com>.
HIVE-6414 seems bad enough to included.
On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> glaring bug on usage of mapred.min.split.size.per.rack and
> mapred.min.split.size.per.node, and makes sure some of the other conf
> parameters we use are correctly through shims. I want this to go into
> 0.13 because I don't want a release of ours to go out with the
> dual/old configs (and erroneous config in the per.rack/node case) and
> have that be expected behaviour to support in the future.
>
> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hb...@hortonworks.com>
> wrote:
> > ok sure.
> > Tracking these with the JQL below. I don’t have permission to setup a
> Shared Filter; can someone help with this.
> > Of the 35 issues: 11 are still open, 22 are patch available, 2 are
> resolved.
> >
> > regards,
> > Harish.
> >
> > JQL:
> >
> > id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687,
> HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455,
> HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507,
> HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293,
> HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752,
> HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC,
> assignee
> >
> > On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <
> pjayachandran@hortonworks.com> wrote:
> >
> >> Can you consider HIVE-6562 as well?
> >>
> >> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
> >>
> >> Thanks
> >> Prasanth Jayachandran
> >>
> >> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
> >>
> >>>
> >>> Would like to get these in, if possible:
> >>>
> >>> HIVE-6012 restore backward compatibility of arithmetic operations
> >>> HIVE-6434 Restrict function create/drop to admin roles
> >>>
> >>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> >>>
> >>>> I have really big wish list(65 pending) but it would be time to focus
> on
> >>>> finalization.
> >>>>
> >>>> - Small bugs
> >>>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
> >>>> HIVE-4790 MapredLocalTask task does not make virtual columns
> >>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
> >>>>
> >>>> - Trivials
> >>>> HIVE-6551 group by after join with skew join optimization references
> >>>> invalid task sometimes
> >>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
> >>>> HIVE-6314 The logging (progress reporting) is too verbose
> >>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> >>>> HIVE-5768 Beeline connection cannot be closed with !close command
> >>>> HIVE-2752 Index names are case sensitive
> >>>>
> >>>> - Memory leakage
> >>>> HIVE-6312 doAs with plain sasl auth should be session aware
> >>>>
> >>>> - Implementation is not accord with document
> >>>> HIVE-6129 alter exchange is implemented in inverted manner
> >>>>
> >>>> I'll update the wiki, too.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
> >>>>
> >>>>> Tracking jiras to be applied to branch 0.13 here:
> >>>>>
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
> >>>>>
> >>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com>
> wrote:
> >>>>>
> >>>>>> the branch is created.
> >>>>>> have changed the poms in both branches.
> >>>>>> Planning to setup a wikipage to track jiras that will get ported to
> 0.13
> >>>>>>
> >>>>>> regards,
> >>>>>> Harish.
> >>>>>>
> >>>>>>
> >>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
> >>>>> wrote:
> >>>>>>
> >>>>>>> branching now. Will be changing the pom files on trunk.
> >>>>>>> Will send another email when the branch and trunk changes are in.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
> >>>>> wrote:
> >>>>>>>
> >>>>>>>> I have two patches still as patch-available, that have had +1s as
> >>>>>>>> well, but are waiting on pre-commit tests picking them up go in to
> >>>>>>>> 0.13:
> >>>>>>>>
> >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of
> table
> >>>>>>>> property names from string constants to an enum in OrcFile)
> >>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where
> calls
> >>>>>>>> like create table and drop table can fail if metastore-side
> >>>>>>>> authorization is used in conjunction with custom
> >>>>>>>> inputformat/outputformat/serdes that are not loadable from the
> >>>>>>>> metastore-side)
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Thejas Nair <th...@hortonworks.com>.
It would be great to have this in -
HIVE-5901 (driver cancel to kill the MR job) has been +1, waiting for
tests to finish.
HIVE-5099 (datanucleues version upgrade) +1'd, waiting for tests to finish.
On Thu, Mar 6, 2014 at 3:28 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
> One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
> for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
> glaring bug on usage of mapred.min.split.size.per.rack and
> mapred.min.split.size.per.node, and makes sure some of the other conf
> parameters we use are correctly through shims. I want this to go into
> 0.13 because I don't want a release of ours to go out with the
> dual/old configs (and erroneous config in the per.rack/node case) and
> have that be expected behaviour to support in the future.
>
> On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hb...@hortonworks.com> wrote:
>> ok sure.
>> Tracking these with the JQL below. I don’t have permission to setup a Shared Filter; can someone help with this.
>> Of the 35 issues: 11 are still open, 22 are patch available, 2 are resolved.
>>
>> regards,
>> Harish.
>>
>> JQL:
>>
>> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687, HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455, HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507, HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293, HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752, HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC, assignee
>>
>> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <pj...@hortonworks.com> wrote:
>>
>>> Can you consider HIVE-6562 as well?
>>>
>>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>>
>>> Thanks
>>> Prasanth Jayachandran
>>>
>>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
>>>
>>>>
>>>> Would like to get these in, if possible:
>>>>
>>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>>> HIVE-6434 Restrict function create/drop to admin roles
>>>>
>>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>>
>>>>> I have really big wish list(65 pending) but it would be time to focus on
>>>>> finalization.
>>>>>
>>>>> - Small bugs
>>>>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
>>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>>
>>>>> - Trivials
>>>>> HIVE-6551 group by after join with skew join optimization references
>>>>> invalid task sometimes
>>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>>> HIVE-5768 Beeline connection cannot be closed with !close command
>>>>> HIVE-2752 Index names are case sensitive
>>>>>
>>>>> - Memory leakage
>>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>>
>>>>> - Implementation is not accord with document
>>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>>
>>>>> I'll update the wiki, too.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>>>>>
>>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>>
>>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>>>>>>
>>>>>>> the branch is created.
>>>>>>> have changed the poms in both branches.
>>>>>>> Planning to setup a wikipage to track jiras that will get ported to 0.13
>>>>>>>
>>>>>>> regards,
>>>>>>> Harish.
>>>>>>>
>>>>>>>
>>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>>> Will send another email when the branch and trunk changes are in.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I have two patches still as patch-available, that have had +1s as
>>>>>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>>>>>> 0.13:
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>>> authorization is used in conjunction with custom
>>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>>>>>> metastore-side)
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Sushanth Sowmyan <kh...@gmail.com>.
One more, I'm afraid. I'll add it to the wiki. I just uploaded a patch
for https://issues.apache.org/jira/browse/HIVE-6572 . This fixes one
glaring bug on usage of mapred.min.split.size.per.rack and
mapred.min.split.size.per.node, and makes sure some of the other conf
parameters we use are correctly through shims. I want this to go into
0.13 because I don't want a release of ours to go out with the
dual/old configs (and erroneous config in the per.rack/node case) and
have that be expected behaviour to support in the future.
On Thu, Mar 6, 2014 at 11:04 AM, Harish Butani <hb...@hortonworks.com> wrote:
> ok sure.
> Tracking these with the JQL below. I don’t have permission to setup a Shared Filter; can someone help with this.
> Of the 35 issues: 11 are still open, 22 are patch available, 2 are resolved.
>
> regards,
> Harish.
>
> JQL:
>
> id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687, HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455, HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507, HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293, HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752, HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC, assignee
>
> On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <pj...@hortonworks.com> wrote:
>
>> Can you consider HIVE-6562 as well?
>>
>> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>>
>> Thanks
>> Prasanth Jayachandran
>>
>> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
>>
>>>
>>> Would like to get these in, if possible:
>>>
>>> HIVE-6012 restore backward compatibility of arithmetic operations
>>> HIVE-6434 Restrict function create/drop to admin roles
>>>
>>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>>
>>>> I have really big wish list(65 pending) but it would be time to focus on
>>>> finalization.
>>>>
>>>> - Small bugs
>>>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
>>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>>
>>>> - Trivials
>>>> HIVE-6551 group by after join with skew join optimization references
>>>> invalid task sometimes
>>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>>> HIVE-6314 The logging (progress reporting) is too verbose
>>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>>> HIVE-5768 Beeline connection cannot be closed with !close command
>>>> HIVE-2752 Index names are case sensitive
>>>>
>>>> - Memory leakage
>>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>>
>>>> - Implementation is not accord with document
>>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>>
>>>> I'll update the wiki, too.
>>>>
>>>>
>>>>
>>>>
>>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>>>>
>>>>> Tracking jiras to be applied to branch 0.13 here:
>>>>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>>
>>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>>>>>
>>>>>> the branch is created.
>>>>>> have changed the poms in both branches.
>>>>>> Planning to setup a wikipage to track jiras that will get ported to 0.13
>>>>>>
>>>>>> regards,
>>>>>> Harish.
>>>>>>
>>>>>>
>>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>>>>> wrote:
>>>>>>
>>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>>> Will send another email when the branch and trunk changes are in.
>>>>>>>
>>>>>>>
>>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>>>>> wrote:
>>>>>>>
>>>>>>>> I have two patches still as patch-available, that have had +1s as
>>>>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>>>>> 0.13:
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>>> authorization is used in conjunction with custom
>>>>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>>>>> metastore-side)
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
ok sure.
Tracking these with the JQL below. I don’t have permission to setup a Shared Filter; can someone help with this.
Of the 35 issues: 11 are still open, 22 are patch available, 2 are resolved.
regards,
Harish.
JQL:
id in (HIVE-5317, HIVE-5843, HIVE-6060, HIVE-6319, HIVE-6460, HIVE-5687, HIVE-5943, HIVE-5942, HIVE-6547, HIVE-5155, HIVE-6486, HIVE-6455, HIVE-4177, HIVE-4764, HIVE-6306, HIVE-6350, HIVE-6485, HIVE-6507, HIVE-6499, HIVE-6325, HIVE-6558, HIVE-6403, HIVE-4790, HIVE-4293, HIVE-6551, HIVE-6359, HIVE-6314, HIVE-6241, HIVE-5768, HIVE-2752, HIVE-6312, HIVE-6129, HIVE-6012, HIVE-6434, HIVE-6562) ORDER BY status ASC, assignee
On Mar 5, 2014, at 6:50 PM, Prasanth Jayachandran <pj...@hortonworks.com> wrote:
> Can you consider HIVE-6562 as well?
>
> HIVE-6562 - Protection from exceptions in ORC predicate evaluation
>
> Thanks
> Prasanth Jayachandran
>
> On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
>
>>
>> Would like to get these in, if possible:
>>
>> HIVE-6012 restore backward compatibility of arithmetic operations
>> HIVE-6434 Restrict function create/drop to admin roles
>>
>> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>>
>>> I have really big wish list(65 pending) but it would be time to focus on
>>> finalization.
>>>
>>> - Small bugs
>>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
>>> HIVE-4790 MapredLocalTask task does not make virtual columns
>>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>>
>>> - Trivials
>>> HIVE-6551 group by after join with skew join optimization references
>>> invalid task sometimes
>>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>>> HIVE-6314 The logging (progress reporting) is too verbose
>>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>>> HIVE-5768 Beeline connection cannot be closed with !close command
>>> HIVE-2752 Index names are case sensitive
>>>
>>> - Memory leakage
>>> HIVE-6312 doAs with plain sasl auth should be session aware
>>>
>>> - Implementation is not accord with document
>>> HIVE-6129 alter exchange is implemented in inverted manner
>>>
>>> I'll update the wiki, too.
>>>
>>>
>>>
>>>
>>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>>>
>>>> Tracking jiras to be applied to branch 0.13 here:
>>>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>>
>>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>>>>
>>>>> the branch is created.
>>>>> have changed the poms in both branches.
>>>>> Planning to setup a wikipage to track jiras that will get ported to 0.13
>>>>>
>>>>> regards,
>>>>> Harish.
>>>>>
>>>>>
>>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>>>> wrote:
>>>>>
>>>>>> branching now. Will be changing the pom files on trunk.
>>>>>> Will send another email when the branch and trunk changes are in.
>>>>>>
>>>>>>
>>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>>> I have two patches still as patch-available, that have had +1s as
>>>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>>>> 0.13:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>>>>>> property names from string constants to an enum in OrcFile)
>>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>>>>>> like create table and drop table can fail if metastore-side
>>>>>>> authorization is used in conjunction with custom
>>>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>>>> metastore-side)
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Prasanth Jayachandran <pj...@hortonworks.com>.
Can you consider HIVE-6562 as well?
HIVE-6562 - Protection from exceptions in ORC predicate evaluation
Thanks
Prasanth Jayachandran
On Mar 5, 2014, at 5:56 PM, Jason Dere <jd...@hortonworks.com> wrote:
>
> Would like to get these in, if possible:
>
> HIVE-6012 restore backward compatibility of arithmetic operations
> HIVE-6434 Restrict function create/drop to admin roles
>
> On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
>
>> I have really big wish list(65 pending) but it would be time to focus on
>> finalization.
>>
>> - Small bugs
>> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
>> HIVE-4790 MapredLocalTask task does not make virtual columns
>> HIVE-4293 Predicates following UDTF operator are removed by PPD
>>
>> - Trivials
>> HIVE-6551 group by after join with skew join optimization references
>> invalid task sometimes
>> HIVE-6359 beeline -f fails on scripts with tabs in them.
>> HIVE-6314 The logging (progress reporting) is too verbose
>> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
>> HIVE-5768 Beeline connection cannot be closed with !close command
>> HIVE-2752 Index names are case sensitive
>>
>> - Memory leakage
>> HIVE-6312 doAs with plain sasl auth should be session aware
>>
>> - Implementation is not accord with document
>> HIVE-6129 alter exchange is implemented in inverted manner
>>
>> I'll update the wiki, too.
>>
>>
>>
>>
>> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>>
>>> Tracking jiras to be applied to branch 0.13 here:
>>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>>
>>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>>>
>>>> the branch is created.
>>>> have changed the poms in both branches.
>>>> Planning to setup a wikipage to track jiras that will get ported to 0.13
>>>>
>>>> regards,
>>>> Harish.
>>>>
>>>>
>>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>>> wrote:
>>>>
>>>>> branching now. Will be changing the pom files on trunk.
>>>>> Will send another email when the branch and trunk changes are in.
>>>>>
>>>>>
>>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>>> wrote:
>>>>>
>>>>>> I have two patches still as patch-available, that have had +1s as
>>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>>> 0.13:
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>>>>> property names from string constants to an enum in OrcFile)
>>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>>>>> like create table and drop table can fail if metastore-side
>>>>>> authorization is used in conjunction with custom
>>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>>> metastore-side)
>>>>>
>>>>
>>>
>>>
>>> --
>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Jason Dere <jd...@hortonworks.com>.
Would like to get these in, if possible:
HIVE-6012 restore backward compatibility of arithmetic operations
HIVE-6434 Restrict function create/drop to admin roles
On Mar 5, 2014, at 5:41 PM, Navis류승우 <na...@nexr.com> wrote:
> I have really big wish list(65 pending) but it would be time to focus on
> finalization.
>
> - Small bugs
> HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
> HIVE-4790 MapredLocalTask task does not make virtual columns
> HIVE-4293 Predicates following UDTF operator are removed by PPD
>
> - Trivials
> HIVE-6551 group by after join with skew join optimization references
> invalid task sometimes
> HIVE-6359 beeline -f fails on scripts with tabs in them.
> HIVE-6314 The logging (progress reporting) is too verbose
> HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
> HIVE-5768 Beeline connection cannot be closed with !close command
> HIVE-2752 Index names are case sensitive
>
> - Memory leakage
> HIVE-6312 doAs with plain sasl auth should be session aware
>
> - Implementation is not accord with document
> HIVE-6129 alter exchange is implemented in inverted manner
>
> I'll update the wiki, too.
>
>
>
>
> 2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
>
>> Tracking jiras to be applied to branch 0.13 here:
>> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>>
>> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>>
>>> the branch is created.
>>> have changed the poms in both branches.
>>> Planning to setup a wikipage to track jiras that will get ported to 0.13
>>>
>>> regards,
>>> Harish.
>>>
>>>
>>> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
>> wrote:
>>>
>>>> branching now. Will be changing the pom files on trunk.
>>>> Will send another email when the branch and trunk changes are in.
>>>>
>>>>
>>>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
>> wrote:
>>>>
>>>>> I have two patches still as patch-available, that have had +1s as
>>>>> well, but are waiting on pre-commit tests picking them up go in to
>>>>> 0.13:
>>>>>
>>>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>>>> property names from string constants to an enum in OrcFile)
>>>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>>>> like create table and drop table can fail if metastore-side
>>>>> authorization is used in conjunction with custom
>>>>> inputformat/outputformat/serdes that are not loadable from the
>>>>> metastore-side)
>>>>
>>>
>>
>>
>> --
>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Navis류승우 <na...@nexr.com>.
I have really big wish list(65 pending) but it would be time to focus on
finalization.
- Small bugs
HIVE-6403 uncorrelated subquery is failing with auto.convert.join=true
HIVE-4790 MapredLocalTask task does not make virtual columns
HIVE-4293 Predicates following UDTF operator are removed by PPD
- Trivials
HIVE-6551 group by after join with skew join optimization references
invalid task sometimes
HIVE-6359 beeline -f fails on scripts with tabs in them.
HIVE-6314 The logging (progress reporting) is too verbose
HIVE-6241 Remove direct reference of Hadoop23Shims inQTestUtil
HIVE-5768 Beeline connection cannot be closed with !close command
HIVE-2752 Index names are case sensitive
- Memory leakage
HIVE-6312 doAs with plain sasl auth should be session aware
- Implementation is not accord with document
HIVE-6129 alter exchange is implemented in inverted manner
I'll update the wiki, too.
2014-03-05 12:18 GMT+09:00 Harish Butani <hb...@hortonworks.com>:
> Tracking jiras to be applied to branch 0.13 here:
> https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
>
> On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
>
> > the branch is created.
> > have changed the poms in both branches.
> > Planning to setup a wikipage to track jiras that will get ported to 0.13
> >
> > regards,
> > Harish.
> >
> >
> > On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com>
> wrote:
> >
> >> branching now. Will be changing the pom files on trunk.
> >> Will send another email when the branch and trunk changes are in.
> >>
> >>
> >> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com>
> wrote:
> >>
> >>> I have two patches still as patch-available, that have had +1s as
> >>> well, but are waiting on pre-commit tests picking them up go in to
> >>> 0.13:
> >>>
> >>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
> >>> property names from string constants to an enum in OrcFile)
> >>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
> >>> like create table and drop table can fail if metastore-side
> >>> authorization is used in conjunction with custom
> >>> inputformat/outputformat/serdes that are not loadable from the
> >>> metastore-side)
> >>
> >
>
>
> --
> 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.
>
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
Tracking jiras to be applied to branch 0.13 here: https://cwiki.apache.org/confluence/display/Hive/Hive+0.13+release+status
On Mar 4, 2014, at 5:45 PM, Harish Butani <hb...@hortonworks.com> wrote:
> the branch is created.
> have changed the poms in both branches.
> Planning to setup a wikipage to track jiras that will get ported to 0.13
>
> regards,
> Harish.
>
>
> On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com> wrote:
>
>> branching now. Will be changing the pom files on trunk.
>> Will send another email when the branch and trunk changes are in.
>>
>>
>> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
>>
>>> I have two patches still as patch-available, that have had +1s as
>>> well, but are waiting on pre-commit tests picking them up go in to
>>> 0.13:
>>>
>>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>>> property names from string constants to an enum in OrcFile)
>>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>>> like create table and drop table can fail if metastore-side
>>> authorization is used in conjunction with custom
>>> inputformat/outputformat/serdes that are not loadable from the
>>> metastore-side)
>>
>
--
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.
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
the branch is created.
have changed the poms in both branches.
Planning to setup a wikipage to track jiras that will get ported to 0.13
regards,
Harish.
On Mar 4, 2014, at 5:05 PM, Harish Butani <hb...@hortonworks.com> wrote:
> branching now. Will be changing the pom files on trunk.
> Will send another email when the branch and trunk changes are in.
>
>
> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
>
>> I have two patches still as patch-available, that have had +1s as
>> well, but are waiting on pre-commit tests picking them up go in to
>> 0.13:
>>
>> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
>> property names from string constants to an enum in OrcFile)
>> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
>> like create table and drop table can fail if metastore-side
>> authorization is used in conjunction with custom
>> inputformat/outputformat/serdes that are not loadable from the
>> metastore-side)
>
--
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.
Re: Timeline for the Hive 0.13 release?
Posted by Vikram Dixit <vi...@hortonworks.com>.
Hi,
I have https://issues.apache.org/jira/browse/HIVE-6325 in patch available.
It is awaiting pre-commit tests to run. I would like for it to go in as
well.
Thanks
Vikram.
On Tue, Mar 4, 2014 at 5:05 PM, Harish Butani <hb...@hortonworks.com>wrote:
> branching now. Will be changing the pom files on trunk.
> Will send another email when the branch and trunk changes are in.
>
>
> On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
>
> > I have two patches still as patch-available, that have had +1s as
> > well, but are waiting on pre-commit tests picking them up go in to
> > 0.13:
> >
> > https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
> > property names from string constants to an enum in OrcFile)
> > https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
> > like create table and drop table can fail if metastore-side
> > authorization is used in conjunction with custom
> > inputformat/outputformat/serdes that are not loadable from the
> > metastore-side)
>
>
> --
> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
branching now. Will be changing the pom files on trunk.
Will send another email when the branch and trunk changes are in.
On Mar 4, 2014, at 4:03 PM, Sushanth Sowmyan <kh...@gmail.com> wrote:
> I have two patches still as patch-available, that have had +1s as
> well, but are waiting on pre-commit tests picking them up go in to
> 0.13:
>
> https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
> property names from string constants to an enum in OrcFile)
> https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
> like create table and drop table can fail if metastore-side
> authorization is used in conjunction with custom
> inputformat/outputformat/serdes that are not loadable from the
> metastore-side)
--
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.
Re: Timeline for the Hive 0.13 release?
Posted by Sushanth Sowmyan <kh...@gmail.com>.
I have two patches still as patch-available, that have had +1s as
well, but are waiting on pre-commit tests picking them up go in to
0.13:
https://issues.apache.org/jira/browse/HIVE-6507 (refactor of table
property names from string constants to an enum in OrcFile)
https://issues.apache.org/jira/browse/HIVE-6499 (fixes bug where calls
like create table and drop table can fail if metastore-side
authorization is used in conjunction with custom
inputformat/outputformat/serdes that are not loadable from the
metastore-side)
Re: Timeline for the Hive 0.13 release?
Posted by Vaibhav Gumashta <vg...@hortonworks.com>.
I'd like to have the following go in:
HIVE-4764 [Support Kerberos HTTP authentication for HiveServer2 running in
http mode] <https://issues.apache.org/jira/browse/HIVE-4764>
HIVE-6306 [HiveServer2 running in http mode should support for doAs
functionality] <https://issues.apache.org/jira/browse/HIVE-6306>
HIVE-6350 [Support LDAP authentication for HiveServer2 in http
mode]<https://issues.apache.org/jira/browse/HIVE-6350>
HIVE-6485 [Downgrade to httpclient-4.2.5 in JDBC from
httpclient-4.3.2]<https://issues.apache.org/jira/browse/HIVE-6485>
And it would awesome to have HIVE-5155 - (proxy user support for HS2).
Thanks,
--Vaibhav
On Tue, Mar 4, 2014 at 1:15 PM, Prasanth Jayachandran <
pjayachandran@hortonworks.com> wrote:
> I would like HIVE-6455 and HIVE-4177 to go in the release.
> HIVE-6455 - Scalable dynamic partitioning optimization (I already have a
> patch for it and is under code review)
> HIVE-4177 - Support partial scan for analyze command - ORC (I will post a
> patch within this week)
>
> Thanks
> Prasanth Jayachandran
>
> On Mar 4, 2014, at 12:13 PM, Thejas Nair <th...@hortonworks.com> wrote:
>
> > I would like to include HIVE-5943/HIVE-5942 (describe role support ) and
> > HIVE-6547 (metastore api - Role struct cleanup) in the release. I should
> > have the patch for describe-role ready in a day or two, and for HIVE-6547
> > as well this week.
> >
> >
> >
> > On Tue, Mar 4, 2014 at 11:55 AM, Harish Butani <hbutani@hortonworks.com
> >wrote:
> >
> >> Yes sure. I am fine with porting over HIVE-5317 and dependents.
> >> Besides, couldn't handle 104 angry fans (uh watchers) :)
> >>
> >> Let’s follow this procedure: if you have features that should go into
> >> branch-0.13 please post a message here, give the community a chance to
> >> voice their opinions.
> >>
> >> regards,
> >> Harish.
> >>
> >>
> >> On Mar 4, 2014, at 8:03 AM, Alan Gates <ga...@hortonworks.com> wrote:
> >>
> >>> Sure. I’d really like to get the work related to HIVE-5317 in 0.13.
> >> HIVE-5843 is patch available and hopefully can be checked in today.
> There
> >> are several more that depend on that one and can’t be made patch
> available
> >> until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t
> want
> >> to hold up the branching, but are you ok with those going in after the
> >> branch?
> >>>
> >>> Alan.
> >>>
> >>> On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com>
> >> wrote:
> >>>
> >>>> I plan to create the branch 5pm PST tomorrow.
> >>>> Ok with everybody?
> >>>>
> >>>> regards,
> >>>> Harish.
> >>>>
> >>>> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com>
> >> wrote:
> >>>>
> >>>>> That's appropriate -- let the Hive release march forth on March 4th.
> >>>>>
> >>>>>
> >>>>> -- Lefty
> >>>>>
> >>>>>
> >>>>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <
> >> hbutani@hortonworks.com>wrote:
> >>>>>
> >>>>>> Ok,let’s set it for March 4th .
> >>>>>>
> >>>>>> regards,
> >>>>>> Harish.
> >>>>>>
> >>>>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com>
> >> wrote:
> >>>>>>
> >>>>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
> >>>>>>> weekend time to get patches in.
> >>>>>>>
> >>>>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <
> >> hbutani@hortonworks.com>
> >>>>>> wrote:
> >>>>>>>> Yes makes sense.
> >>>>>>>> How about we postpone the branching until 10am PST March 3rd,
> which
> >> is
> >>>>>> the following Monday.
> >>>>>>>> Don’t see a point of setting the branch time to a Friday evening.
> >>>>>>>> Do people agree?
> >>>>>>>>
> >>>>>>>> regards,
> >>>>>>>> Harish.
> >>>>>>>>
> >>>>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com>
> >> wrote:
> >>>>>>>>
> >>>>>>>>> +1
> >>>>>>>>>
> >>>>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <
> >> thejas@hortonworks.com>
> >>>>>> wrote:
> >>>>>>>>>> Can we wait for some few more days for the branching ? I have a
> >> few
> >>>>>> more
> >>>>>>>>>> security fixes that I would like to get in, and we also have a
> >> long
> >>>>>>>>>> pre-commit queue ahead right now. How about branching around
> >> Friday
> >>>>>> next
> >>>>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has
> >> been
> >>>>>>>>>> concluded, and we can get HIVE-6037 in as well.
> >>>>>>>>>> -Thejas
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <
> brock@cloudera.com
> >>>
> >>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
> >>>>>> pending
> >>>>>>>>>>> tests.
> >>>>>>>>>>>
> >>>>>>>>>>> Brock
> >>>>>>>>>>>
> >>>>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
> >>>>>> wrote:
> >>>>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
> >>>>>> HiveConf.
> >>>>>>>>>>> Could
> >>>>>>>>>>>> it be included in this release? If it's not, I'll suspend
> >> further
> >>>>>>>>>>> rebasing
> >>>>>>>>>>>> of it till next release (conflicts too frequently).
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <
> >> leftyleverenz@gmail.com
> >>>>>>> :
> >>>>>>>>>>>>
> >>>>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0
> >> patches in
> >>>>>> time
> >>>>>>>>>>> for
> >>>>>>>>>>>>> the release. It's a long and growing list, though, so no
> >> promises.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
> >>>>>> friendly
> >>>>>>>>>>>>> in-house writer.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
> >>>>>> thejas@hortonworks.com>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Sounds good to me.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
> >>>>>>>>>>> hbutani@hortonworks.com
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to
> >> cut a
> >>>>>>>>>>> branch.
> >>>>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
> >>>>>>>>>>>>>>> The goal is to keep the release cycle short: couple of
> >> weeks; so
> >>>>>>>>>>> after
> >>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking
> in
> >>>>>> only
> >>>>>>>>>>>>>>> blocker/critical bug fixes.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> regards,
> >>>>>>>>>>>>>>> Harish.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <
> >> brock@cloudera.com>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
> >>>>>>>>>>> commits to
> >>>>>>>>>>>>>>> that
> >>>>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Brock
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
> >>>>>>>>>>>>>> hbutani@hortonworks.com
> >>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Yes agree it is time to start planning for the next
> >> release.
> >>>>>>>>>>>>>>>>> I would like to volunteer to do the release management
> >> duties
> >>>>>> for
> >>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>> release(will be a great experience for me)
> >>>>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with
> this.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> regards,
> >>>>>>>>>>>>>>>>> Harish.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
> >>>>>> thejas@hortonworks.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
> >>>>>> release.
> >>>>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted
> >> patches
> >>>>>>>>>>> that
> >>>>>>>>>>>>>>>>>> people asked to be included for sometime, before moving
> a
> >>>>>> phase
> >>>>>>>>>>> of
> >>>>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
> >>>>>>>>>>> laborious.
> >>>>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to
> >> get any
> >>>>>>>>>>>>>> patches
> >>>>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and
> take
> >> in
> >>>>>>>>>>> only
> >>>>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
> >>>>>>>>>>>>>>>>>> How about cutting the branch around mid-February and
> >> targeting
> >>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> release in a week or two after that.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>>> Thejas
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
> >>>>>> cws@apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>>> I was wondering what people think about setting a
> >> tentative
> >>>>>>>>>>> date
> >>>>>>>>>>>>> for
> >>>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we
> >> agreed
> >>>>>>>>>>> that
> >>>>>>>>>>>>>> Hive
> >>>>>>>>>>>>>>>>>>> should follow a time-based release model with new
> >> releases
> >>>>>>>>>>> every
> >>>>>>>>>>>>>> four
> >>>>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the
> next
> >>>>>>>>>>> release
> >>>>>>>>>>>>> in
> >>>>>>>>>>>>>>>>>>> mid-February.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thoughts?
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Thanks.
> >>>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>> Carl
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> 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.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
> >>>>>> http://mrunit.apache.org
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>> 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.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
> >> http://mrunit.apache.org
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> 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.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Apache MRUnit - Unit testing MapReduce -
> http://mrunit.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> 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.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Prasanth Jayachandran <pj...@hortonworks.com>.
I would like HIVE-6455 and HIVE-4177 to go in the release.
HIVE-6455 - Scalable dynamic partitioning optimization (I already have a patch for it and is under code review)
HIVE-4177 - Support partial scan for analyze command - ORC (I will post a patch within this week)
Thanks
Prasanth Jayachandran
On Mar 4, 2014, at 12:13 PM, Thejas Nair <th...@hortonworks.com> wrote:
> I would like to include HIVE-5943/HIVE-5942 (describe role support ) and
> HIVE-6547 (metastore api - Role struct cleanup) in the release. I should
> have the patch for describe-role ready in a day or two, and for HIVE-6547
> as well this week.
>
>
>
> On Tue, Mar 4, 2014 at 11:55 AM, Harish Butani <hb...@hortonworks.com>wrote:
>
>> Yes sure. I am fine with porting over HIVE-5317 and dependents.
>> Besides, couldn't handle 104 angry fans (uh watchers) :)
>>
>> Let’s follow this procedure: if you have features that should go into
>> branch-0.13 please post a message here, give the community a chance to
>> voice their opinions.
>>
>> regards,
>> Harish.
>>
>>
>> On Mar 4, 2014, at 8:03 AM, Alan Gates <ga...@hortonworks.com> wrote:
>>
>>> Sure. I’d really like to get the work related to HIVE-5317 in 0.13.
>> HIVE-5843 is patch available and hopefully can be checked in today. There
>> are several more that depend on that one and can’t be made patch available
>> until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t want
>> to hold up the branching, but are you ok with those going in after the
>> branch?
>>>
>>> Alan.
>>>
>>> On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com>
>> wrote:
>>>
>>>> I plan to create the branch 5pm PST tomorrow.
>>>> Ok with everybody?
>>>>
>>>> regards,
>>>> Harish.
>>>>
>>>> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com>
>> wrote:
>>>>
>>>>> That's appropriate -- let the Hive release march forth on March 4th.
>>>>>
>>>>>
>>>>> -- Lefty
>>>>>
>>>>>
>>>>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <
>> hbutani@hortonworks.com>wrote:
>>>>>
>>>>>> Ok,let’s set it for March 4th .
>>>>>>
>>>>>> regards,
>>>>>> Harish.
>>>>>>
>>>>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com>
>> wrote:
>>>>>>
>>>>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
>>>>>>> weekend time to get patches in.
>>>>>>>
>>>>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <
>> hbutani@hortonworks.com>
>>>>>> wrote:
>>>>>>>> Yes makes sense.
>>>>>>>> How about we postpone the branching until 10am PST March 3rd, which
>> is
>>>>>> the following Monday.
>>>>>>>> Don’t see a point of setting the branch time to a Friday evening.
>>>>>>>> Do people agree?
>>>>>>>>
>>>>>>>> regards,
>>>>>>>> Harish.
>>>>>>>>
>>>>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com>
>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <
>> thejas@hortonworks.com>
>>>>>> wrote:
>>>>>>>>>> Can we wait for some few more days for the branching ? I have a
>> few
>>>>>> more
>>>>>>>>>> security fixes that I would like to get in, and we also have a
>> long
>>>>>>>>>> pre-commit queue ahead right now. How about branching around
>> Friday
>>>>>> next
>>>>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has
>> been
>>>>>>>>>> concluded, and we can get HIVE-6037 in as well.
>>>>>>>>>> -Thejas
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <brock@cloudera.com
>>>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
>>>>>> pending
>>>>>>>>>>> tests.
>>>>>>>>>>>
>>>>>>>>>>> Brock
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
>>>>>> wrote:
>>>>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
>>>>>> HiveConf.
>>>>>>>>>>> Could
>>>>>>>>>>>> it be included in this release? If it's not, I'll suspend
>> further
>>>>>>>>>>> rebasing
>>>>>>>>>>>> of it till next release (conflicts too frequently).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <
>> leftyleverenz@gmail.com
>>>>>>> :
>>>>>>>>>>>>
>>>>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0
>> patches in
>>>>>> time
>>>>>>>>>>> for
>>>>>>>>>>>>> the release. It's a long and growing list, though, so no
>> promises.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
>>>>>> friendly
>>>>>>>>>>>>> in-house writer.
>>>>>>>>>>>>>
>>>>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
>>>>>> thejas@hortonworks.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sounds good to me.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
>>>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to
>> cut a
>>>>>>>>>>> branch.
>>>>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
>>>>>>>>>>>>>>> The goal is to keep the release cycle short: couple of
>> weeks; so
>>>>>>>>>>> after
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking in
>>>>>> only
>>>>>>>>>>>>>>> blocker/critical bug fixes.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> regards,
>>>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <
>> brock@cloudera.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
>>>>>>>>>>> commits to
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Brock
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
>>>>>>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Yes agree it is time to start planning for the next
>> release.
>>>>>>>>>>>>>>>>> I would like to volunteer to do the release management
>> duties
>>>>>> for
>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>> release(will be a great experience for me)
>>>>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> regards,
>>>>>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
>>>>>> thejas@hortonworks.com
>>>>>>>>>>>>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
>>>>>> release.
>>>>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted
>> patches
>>>>>>>>>>> that
>>>>>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
>>>>>> phase
>>>>>>>>>>> of
>>>>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
>>>>>>>>>>> laborious.
>>>>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to
>> get any
>>>>>>>>>>>>>> patches
>>>>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take
>> in
>>>>>>>>>>> only
>>>>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
>>>>>>>>>>>>>>>>>> How about cutting the branch around mid-February and
>> targeting
>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> release in a week or two after that.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Thejas
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
>>>>>> cws@apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>> I was wondering what people think about setting a
>> tentative
>>>>>>>>>>> date
>>>>>>>>>>>>> for
>>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we
>> agreed
>>>>>>>>>>> that
>>>>>>>>>>>>>> Hive
>>>>>>>>>>>>>>>>>>> should follow a time-based release model with new
>> releases
>>>>>>>>>>> every
>>>>>>>>>>>>>> four
>>>>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the next
>>>>>>>>>>> release
>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>>> mid-February.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Carl
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>>>>>> http://mrunit.apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>> http://mrunit.apache.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Thejas Nair <th...@hortonworks.com>.
I would like to include HIVE-5943/HIVE-5942 (describe role support ) and
HIVE-6547 (metastore api - Role struct cleanup) in the release. I should
have the patch for describe-role ready in a day or two, and for HIVE-6547
as well this week.
On Tue, Mar 4, 2014 at 11:55 AM, Harish Butani <hb...@hortonworks.com>wrote:
> Yes sure. I am fine with porting over HIVE-5317 and dependents.
> Besides, couldn't handle 104 angry fans (uh watchers) :)
>
> Let’s follow this procedure: if you have features that should go into
> branch-0.13 please post a message here, give the community a chance to
> voice their opinions.
>
> regards,
> Harish.
>
>
> On Mar 4, 2014, at 8:03 AM, Alan Gates <ga...@hortonworks.com> wrote:
>
> > Sure. I’d really like to get the work related to HIVE-5317 in 0.13.
> HIVE-5843 is patch available and hopefully can be checked in today. There
> are several more that depend on that one and can’t be made patch available
> until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t want
> to hold up the branching, but are you ok with those going in after the
> branch?
> >
> > Alan.
> >
> > On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com>
> wrote:
> >
> >> I plan to create the branch 5pm PST tomorrow.
> >> Ok with everybody?
> >>
> >> regards,
> >> Harish.
> >>
> >> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com>
> wrote:
> >>
> >>> That's appropriate -- let the Hive release march forth on March 4th.
> >>>
> >>>
> >>> -- Lefty
> >>>
> >>>
> >>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <
> hbutani@hortonworks.com>wrote:
> >>>
> >>>> Ok,let’s set it for March 4th .
> >>>>
> >>>> regards,
> >>>> Harish.
> >>>>
> >>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com>
> wrote:
> >>>>
> >>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
> >>>>> weekend time to get patches in.
> >>>>>
> >>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <
> hbutani@hortonworks.com>
> >>>> wrote:
> >>>>>> Yes makes sense.
> >>>>>> How about we postpone the branching until 10am PST March 3rd, which
> is
> >>>> the following Monday.
> >>>>>> Don’t see a point of setting the branch time to a Friday evening.
> >>>>>> Do people agree?
> >>>>>>
> >>>>>> regards,
> >>>>>> Harish.
> >>>>>>
> >>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com>
> wrote:
> >>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <
> thejas@hortonworks.com>
> >>>> wrote:
> >>>>>>>> Can we wait for some few more days for the branching ? I have a
> few
> >>>> more
> >>>>>>>> security fixes that I would like to get in, and we also have a
> long
> >>>>>>>> pre-commit queue ahead right now. How about branching around
> Friday
> >>>> next
> >>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has
> been
> >>>>>>>> concluded, and we can get HIVE-6037 in as well.
> >>>>>>>> -Thejas
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <brock@cloudera.com
> >
> >>>> wrote:
> >>>>>>>>
> >>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
> >>>> pending
> >>>>>>>>> tests.
> >>>>>>>>>
> >>>>>>>>> Brock
> >>>>>>>>>
> >>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
> >>>> wrote:
> >>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
> >>>> HiveConf.
> >>>>>>>>> Could
> >>>>>>>>>> it be included in this release? If it's not, I'll suspend
> further
> >>>>>>>>> rebasing
> >>>>>>>>>> of it till next release (conflicts too frequently).
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <
> leftyleverenz@gmail.com
> >>>>> :
> >>>>>>>>>>
> >>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0
> patches in
> >>>> time
> >>>>>>>>> for
> >>>>>>>>>>> the release. It's a long and growing list, though, so no
> promises.
> >>>>>>>>>>>
> >>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
> >>>> friendly
> >>>>>>>>>>> in-house writer.
> >>>>>>>>>>>
> >>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
> >>>> thejas@hortonworks.com>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Sounds good to me.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
> >>>>>>>>> hbutani@hortonworks.com
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to
> cut a
> >>>>>>>>> branch.
> >>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
> >>>>>>>>>>>>> The goal is to keep the release cycle short: couple of
> weeks; so
> >>>>>>>>> after
> >>>>>>>>>>>> the
> >>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking in
> >>>> only
> >>>>>>>>>>>>> blocker/critical bug fixes.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> regards,
> >>>>>>>>>>>>> Harish.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <
> brock@cloudera.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hi,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
> >>>>>>>>> commits to
> >>>>>>>>>>>>> that
> >>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Brock
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
> >>>>>>>>>>>> hbutani@hortonworks.com
> >>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Yes agree it is time to start planning for the next
> release.
> >>>>>>>>>>>>>>> I would like to volunteer to do the release management
> duties
> >>>> for
> >>>>>>>>>>> this
> >>>>>>>>>>>>>>> release(will be a great experience for me)
> >>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> regards,
> >>>>>>>>>>>>>>> Harish.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
> >>>> thejas@hortonworks.com
> >>>>>>>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
> >>>> release.
> >>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted
> patches
> >>>>>>>>> that
> >>>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
> >>>> phase
> >>>>>>>>> of
> >>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
> >>>>>>>>> laborious.
> >>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to
> get any
> >>>>>>>>>>>> patches
> >>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take
> in
> >>>>>>>>> only
> >>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
> >>>>>>>>>>>>>>>> How about cutting the branch around mid-February and
> targeting
> >>>>>>>>> to
> >>>>>>>>>>>>>>>> release in a week or two after that.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>> Thejas
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
> >>>> cws@apache.org
> >>>>>>>>>>
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>> I was wondering what people think about setting a
> tentative
> >>>>>>>>> date
> >>>>>>>>>>> for
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we
> agreed
> >>>>>>>>> that
> >>>>>>>>>>>> Hive
> >>>>>>>>>>>>>>>>> should follow a time-based release model with new
> releases
> >>>>>>>>> every
> >>>>>>>>>>>> four
> >>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the next
> >>>>>>>>> release
> >>>>>>>>>>> in
> >>>>>>>>>>>>>>>>> mid-February.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Thoughts?
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Thanks.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Carl
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> 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.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
> >>>> http://mrunit.apache.org
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> 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.
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Apache MRUnit - Unit testing MapReduce -
> http://mrunit.apache.org
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> 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.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> 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.
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
> >>>>
> >>>>
> >>>> --
> >>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Harish Butani <hb...@hortonworks.com>.
Yes sure. I am fine with porting over HIVE-5317 and dependents.
Besides, couldn't handle 104 angry fans (uh watchers) :)
Let’s follow this procedure: if you have features that should go into branch-0.13 please post a message here, give the community a chance to voice their opinions.
regards,
Harish.
On Mar 4, 2014, at 8:03 AM, Alan Gates <ga...@hortonworks.com> wrote:
> Sure. I’d really like to get the work related to HIVE-5317 in 0.13. HIVE-5843 is patch available and hopefully can be checked in today. There are several more that depend on that one and can’t be made patch available until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t want to hold up the branching, but are you ok with those going in after the branch?
>
> Alan.
>
> On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com> wrote:
>
>> I plan to create the branch 5pm PST tomorrow.
>> Ok with everybody?
>>
>> regards,
>> Harish.
>>
>> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com> wrote:
>>
>>> That's appropriate -- let the Hive release march forth on March 4th.
>>>
>>>
>>> -- Lefty
>>>
>>>
>>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <hb...@hortonworks.com>wrote:
>>>
>>>> Ok,let’s set it for March 4th .
>>>>
>>>> regards,
>>>> Harish.
>>>>
>>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com> wrote:
>>>>
>>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
>>>>> weekend time to get patches in.
>>>>>
>>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <hb...@hortonworks.com>
>>>> wrote:
>>>>>> Yes makes sense.
>>>>>> How about we postpone the branching until 10am PST March 3rd, which is
>>>> the following Monday.
>>>>>> Don’t see a point of setting the branch time to a Friday evening.
>>>>>> Do people agree?
>>>>>>
>>>>>> regards,
>>>>>> Harish.
>>>>>>
>>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <th...@hortonworks.com>
>>>> wrote:
>>>>>>>> Can we wait for some few more days for the branching ? I have a few
>>>> more
>>>>>>>> security fixes that I would like to get in, and we also have a long
>>>>>>>> pre-commit queue ahead right now. How about branching around Friday
>>>> next
>>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has been
>>>>>>>> concluded, and we can get HIVE-6037 in as well.
>>>>>>>> -Thejas
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <br...@cloudera.com>
>>>> wrote:
>>>>>>>>
>>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
>>>> pending
>>>>>>>>> tests.
>>>>>>>>>
>>>>>>>>> Brock
>>>>>>>>>
>>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
>>>> wrote:
>>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
>>>> HiveConf.
>>>>>>>>> Could
>>>>>>>>>> it be included in this release? If it's not, I'll suspend further
>>>>>>>>> rebasing
>>>>>>>>>> of it till next release (conflicts too frequently).
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <leftyleverenz@gmail.com
>>>>> :
>>>>>>>>>>
>>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0 patches in
>>>> time
>>>>>>>>> for
>>>>>>>>>>> the release. It's a long and growing list, though, so no promises.
>>>>>>>>>>>
>>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
>>>> friendly
>>>>>>>>>>> in-house writer.
>>>>>>>>>>>
>>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
>>>> thejas@hortonworks.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Sounds good to me.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to cut a
>>>>>>>>> branch.
>>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
>>>>>>>>>>>>> The goal is to keep the release cycle short: couple of weeks; so
>>>>>>>>> after
>>>>>>>>>>>> the
>>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking in
>>>> only
>>>>>>>>>>>>> blocker/critical bug fixes.
>>>>>>>>>>>>>
>>>>>>>>>>>>> regards,
>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <br...@cloudera.com>
>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
>>>>>>>>> commits to
>>>>>>>>>>>>> that
>>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Brock
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
>>>>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes agree it is time to start planning for the next release.
>>>>>>>>>>>>>>> I would like to volunteer to do the release management duties
>>>> for
>>>>>>>>>>> this
>>>>>>>>>>>>>>> release(will be a great experience for me)
>>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> regards,
>>>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
>>>> thejas@hortonworks.com
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
>>>> release.
>>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted patches
>>>>>>>>> that
>>>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
>>>> phase
>>>>>>>>> of
>>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
>>>>>>>>> laborious.
>>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to get any
>>>>>>>>>>>> patches
>>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take in
>>>>>>>>> only
>>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
>>>>>>>>>>>>>>>> How about cutting the branch around mid-February and targeting
>>>>>>>>> to
>>>>>>>>>>>>>>>> release in a week or two after that.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>> Thejas
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
>>>> cws@apache.org
>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>> I was wondering what people think about setting a tentative
>>>>>>>>> date
>>>>>>>>>>> for
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we agreed
>>>>>>>>> that
>>>>>>>>>>>> Hive
>>>>>>>>>>>>>>>>> should follow a time-based release model with new releases
>>>>>>>>> every
>>>>>>>>>>>> four
>>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the next
>>>>>>>>> release
>>>>>>>>>>> in
>>>>>>>>>>>>>>>>> mid-February.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Carl
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>>>> http://mrunit.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> 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.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>
>>>>
>>>> --
>>>> 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.
Re: Timeline for the Hive 0.13 release?
Posted by Alan Gates <ga...@hortonworks.com>.
Sure. I’d really like to get the work related to HIVE-5317 in 0.13. HIVE-5843 is patch available and hopefully can be checked in today. There are several more that depend on that one and can’t be made patch available until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I don’t want to hold up the branching, but are you ok with those going in after the branch?
Alan.
On Mar 3, 2014, at 7:53 PM, Harish Butani <hb...@hortonworks.com> wrote:
> I plan to create the branch 5pm PST tomorrow.
> Ok with everybody?
>
> regards,
> Harish.
>
> On Feb 21, 2014, at 5:44 PM, Lefty Leverenz <le...@gmail.com> wrote:
>
>> That's appropriate -- let the Hive release march forth on March 4th.
>>
>>
>> -- Lefty
>>
>>
>> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani <hb...@hortonworks.com>wrote:
>>
>>> Ok,let’s set it for March 4th .
>>>
>>> regards,
>>> Harish.
>>>
>>> On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com> wrote:
>>>
>>>> Might as well make it March 4th or 5th. Otherwise folks will burn
>>>> weekend time to get patches in.
>>>>
>>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <hb...@hortonworks.com>
>>> wrote:
>>>>> Yes makes sense.
>>>>> How about we postpone the branching until 10am PST March 3rd, which is
>>> the following Monday.
>>>>> Don’t see a point of setting the branch time to a Friday evening.
>>>>> Do people agree?
>>>>>
>>>>> regards,
>>>>> Harish.
>>>>>
>>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com> wrote:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <th...@hortonworks.com>
>>> wrote:
>>>>>>> Can we wait for some few more days for the branching ? I have a few
>>> more
>>>>>>> security fixes that I would like to get in, and we also have a long
>>>>>>> pre-commit queue ahead right now. How about branching around Friday
>>> next
>>>>>>> week ? By then hadoop 2.3 should also be out as that vote has been
>>>>>>> concluded, and we can get HIVE-6037 in as well.
>>>>>>> -Thejas
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <br...@cloudera.com>
>>> wrote:
>>>>>>>
>>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it
>>> pending
>>>>>>>> tests.
>>>>>>>>
>>>>>>>> Brock
>>>>>>>>
>>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <na...@nexr.com>
>>> wrote:
>>>>>>>>> HIVE-6037 is for generating hive-default.template file from
>>> HiveConf.
>>>>>>>> Could
>>>>>>>>> it be included in this release? If it's not, I'll suspend further
>>>>>>>> rebasing
>>>>>>>>> of it till next release (conflicts too frequently).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz <leftyleverenz@gmail.com
>>>> :
>>>>>>>>>
>>>>>>>>>> I'll try to catch up on the wikidocs backlog for 0.13.0 patches in
>>> time
>>>>>>>> for
>>>>>>>>>> the release. It's a long and growing list, though, so no promises.
>>>>>>>>>>
>>>>>>>>>> Feel free to do your own documentation, or hand it off to a
>>> friendly
>>>>>>>>>> in-house writer.
>>>>>>>>>>
>>>>>>>>>> -- Lefty, self-appointed Hive docs maven
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <
>>> thejas@hortonworks.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Sounds good to me.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <
>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> Its mid feb. Wanted to check if the community is ready to cut a
>>>>>>>> branch.
>>>>>>>>>>>> Could we cut the branch in a week , say 5pm PST 2/21/14?
>>>>>>>>>>>> The goal is to keep the release cycle short: couple of weeks; so
>>>>>>>> after
>>>>>>>>>>> the
>>>>>>>>>>>> branch we go into stabilizing mode for hive 0.13, checking in
>>> only
>>>>>>>>>>>> blocker/critical bug fixes.
>>>>>>>>>>>>
>>>>>>>>>>>> regards,
>>>>>>>>>>>> Harish.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland <br...@cloudera.com>
>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I agree that picking a date to branch and then restricting
>>>>>>>> commits to
>>>>>>>>>>>> that
>>>>>>>>>>>>> branch would be a less time intensive plan for the RM.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Brock
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani <
>>>>>>>>>>> hbutani@hortonworks.com
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes agree it is time to start planning for the next release.
>>>>>>>>>>>>>> I would like to volunteer to do the release management duties
>>> for
>>>>>>>>>> this
>>>>>>>>>>>>>> release(will be a great experience for me)
>>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> regards,
>>>>>>>>>>>>>> Harish.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair <
>>> thejas@hortonworks.com
>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next
>>> release.
>>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted patches
>>>>>>>> that
>>>>>>>>>>>>>>> people asked to be included for sometime, before moving a
>>> phase
>>>>>>>> of
>>>>>>>>>>>>>>> accepting only critical bug fixes. This turned out to be
>>>>>>>> laborious.
>>>>>>>>>>>>>>> I think we should instead give everyone a few weeks to get any
>>>>>>>>>>> patches
>>>>>>>>>>>>>>> they are working on to be ready, cut the branch, and take in
>>>>>>>> only
>>>>>>>>>>>>>>> critical bug fixes to the branch after that.
>>>>>>>>>>>>>>> How about cutting the branch around mid-February and targeting
>>>>>>>> to
>>>>>>>>>>>>>>> release in a week or two after that.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Thejas
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <
>>> cws@apache.org
>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> I was wondering what people think about setting a tentative
>>>>>>>> date
>>>>>>>>>> for
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we agreed
>>>>>>>> that
>>>>>>>>>>> Hive
>>>>>>>>>>>>>>>> should follow a time-based release model with new releases
>>>>>>>> every
>>>>>>>>>>> four
>>>>>>>>>>>>>>>> months. If we follow that schedule we're due for the next
>>>>>>>> release
>>>>>>>>>> in
>>>>>>>>>>>>>>>> mid-February.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Carl
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> 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.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce -
>>> http://mrunit.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>>>
>>>>>
>>>>> --
>>>>> 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.
>>>>
>>>>
>>>>
>>>> --
>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>
>>>
>>> --
>>> 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.