For TEZ-2000, I verify it does not exist in 0.6.0, only impact the master.
On Wed, Jan 28, 2015 at 4:34 AM, Hitesh Shah <[email protected]> wrote: > @Rohini, are these issues seen with the 0.6.0 release or with the master > branch? Would it be possible for you to re-run against 0.6.0 if you were > running against master? > > thanks > — Hitesh > > On Jan 26, 2015, at 10:41 AM, Rohini Palaniswamy <[email protected]> > wrote: > > > Created TEZ-1999 and TEZ-2000. First one seems to be a patch only in > > master. Haven't checked the other one. > > > > On Mon, Jan 26, 2015 at 8:08 AM, Jonathan Eagles <[email protected]> > wrote: > > > >> Please go ahead and file the issues. In particular, please indicate if > >> this issue is worthy of pulling this release. > >> > >> Jon > >> > >> On Mon, Jan 26, 2015 at 9:17 AM, Rohini Palaniswamy > >> <[email protected]> wrote: > >>> Jon, > >>> I see that this has been already released. But with the latest > >> internal > >>> tez build from master, i see that there are lot of test failures in Pig > >>> most of it due to two different exceptions. I will file jiras today > after > >>> tracking down what jiras caused the problem and whether they went into > >>> 0.6. A patch release might be required based on that. > >>> > >>> Regards, > >>> Rohini > >>> > >>> On Fri, Jan 23, 2015 at 8:29 AM, Sreenath Somarajapuram < > >>> [email protected]> wrote: > >>> > >>>> +1 (non-binding) > >>>> Verified checksums. Build from src and did a smoke on UI. > >>>> > >>>> - Sreenath > >>>> > >>>> On Fri, Jan 23, 2015 at 9:28 PM, Rajesh Balamohan < > >> [email protected]> > >>>> wrote: > >>>> > >>>>> +1 (binding) > >>>>> > >>>>> Verified signatures & checksums. Ran few jobs and they ran > >> successfully. > >>>>> > >>>>> Got an error while running testing. Will file a separate jira for > it. > >>>>> > >>>>> ~Rajesh.B > >>>>> > >>>>> On Fri, Jan 23, 2015 at 7:06 PM, Jianfeng (Jeff) Zhang < > >>>>> [email protected]> wrote: > >>>>> > >>>>>> +1 > >>>>>> > >>>>>> built from source code, and run some tez-example jobs in single-node > >>>>> hadoop > >>>>>> > >>>>>> > >>>>>> Best Regards, > >>>>>> Jeff Zhang > >>>>>> > >>>>>> > >>>>>> On Fri, Jan 23, 2015 at 9:20 PM, Prakash Ramachandran < > >>>>>> [email protected]> wrote: > >>>>>> > >>>>>>> +1 (non-binding) > >>>>>>> verified checksums, built from src and ran jobs locally. > >>>>>>> tested ui functionality > >>>>>>> > >>>>>>> thanks > >>>>>>> Prakash > >>>>>>> > >>>>>>> > >>>>>>> On 1/23/15 1:25 AM, Siddharth Seth wrote: > >>>>>>> > >>>>>>>> +1 (binding). > >>>>>>>> Verified signatures and checksums. Built from src and ran some > >> jobs > >>>>>>>> successfully. > >>>>>>>> > >>>>>>>> Thanks > >>>>>>>> - Sid > >>>>>>>> > >>>>>>>> On Tue, Jan 20, 2015 at 2:05 PM, Jonathan Eagles < > >> [email protected] > >>>>> > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>> I have created an tez-0.6.0 release candidate (rc0). > >>>>>>>>> > >>>>>>>>> GIT source tag > >>>>>>>>> > >>>>>>>>> https://git-wip-us.apache.org/repos/asf/tez/repo?p=tez.git; > >>>>>>>>> a=log;h=refs/tags/release-0.6.0-rc0 > >>>>>>>>> > >>>>>>>>> Staging site: > >>>>>>>>> https://dist.apache.org/repos/dist/dev/tez/tez-0.6.0-src-rc0/ > >>>>>>>>> > >>>>>>>>> Nexus Staging URL: > >>>>>>>>> > >>>>> > https://repository.apache.org/content/repositories/orgapachetez-1019/ > >>>>>>>>> > >>>>>>>>> PGP release keys: > >>>>>>>>> http://pgp.mit.edu/pks/lookup?op=get&search=0x7CF638ACEF9F98AE > >>>>>>>>> > >>>>>>>>> KEYS file available at > >>>>>>>>> https://dist.apache.org/repos/dist/release/tez/KEYS > >>>>>>>>> > >>>>>>>>> List of issues fixed in the release: > >>>>>>>>> > >> https://issues.apache.org/jira/browse/TEZ/fixforversion/12327652/ > >>>>>>>>> > >>>>>>>>> Vote will be open for at least 72 hours and will close on > >> 1/23/2015 > >>>>>>>>> > >>>>>>>>> [ ] +1 approve > >>>>>>>>> [ ] +0 no opinion > >>>>>>>>> [ ] -1 disapprove (and reason why) > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> I begin the vote with my +1. > >>>>>>>>> > >>>>>>>>> Thanks, > >>>>>>>>> jeagles > >>>>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> 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. > >>>> > >> > > -- Best Regards Jeff Zhang
