tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jianfeng (Jeff) Zhang" <jzh...@hortonworks.com>
Subject Re: [VOTE] Merge branch TEZ-2003 into master
Date Thu, 20 Aug 2015 08:21:00 GMT

+1 Did a basic review on the TEZ-2003 branch, and run some pig jobs
successfully based on this branch.


Best Regard,
Jeff Zhang





On 8/20/15, 3:44 PM, "Bikas Saha" <bikas@hortonworks.com> wrote:

>Did a high-level review on the branch. Merging it in will enable
>downstream consumers to make use of the changes and also allow other
>contributors to start participating more in this feature work. To
>facilitate that, we should start doing review then commit going forward
>for future changes. This will help build context around this feature
>among other contributors.
>
>+1
>
>Bikas
>________________________________________
>From: Hitesh Shah <hitesh@apache.org>
>Sent: Wednesday, August 19, 2015 3:54 PM
>To: dev@tez.apache.org
>Subject: Re: [VOTE] Merge branch TEZ-2003 into master
>
>+1.
>
>Did a basic review on the branch. The LLAP/3rd party plugin integration
>will likely take time to stabilize. However, getting this merge done
>sooner into trunk will mean that there will be more folks looking and
>changing the various modified pieces which should be good to harden this
>layer over the longer term.
>
>‹ Hitesh
>
>
>On Aug 17, 2015, at 3:19 PM, Siddharth Seth <sseth@apache.org> wrote:
>
>> Following up from the earlier note about merging the TEZ-2003 branch
>>back
>> into master, this is a vote for the same.
>> 
>>http://mail-archives.apache.org/mod_mbox/tez-dev/201507.mbox/%3CCAOapipvQ
>>y3pUYOsEDz-1UezNMFkwTgpq29reehY9pnH1ShDsxQ%40mail.gmail.com%3E
>> )
>>
>> There've been a bunch of reviews, and comments answered / addressed /
>> tracked for future work, test-patch reports are mostly clean (waiting
>>for
>> a new findbugs report), and the branch has been running with an external
>> service (LLAP - HIVE-7926) on a multi-node cluster for several months.
>>
>> Work will continue on the feature after the merge. There's several
>>pending
>> jiras, which can be worked on after the changes are available in master.
>> Some are simple changes like renames - which will be just before or soon
>> after the merge.
>>
>> After a merge is complete, I'll call for a release off of the 0.8 line
>>- as
>> an alpha, to get the bits available to downstream users, as well as to
>> allow the changes to go through more testing.
>>
>> The vote will is open for at least 72 hours.
>>
>>
>> Thanks
>> - Sid
>
>
>


Mime
View raw message