The first two are concerning. I don't think the scheduler message test failures should block releases.
---------------------------------------- > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: RE: Cutting a release 0.6.5 tonight > Date: Wed, 11 Mar 2015 21:25:15 +0000 > > The test failed are: > > org.apache.helix.integration.TestExternalViewUpdates.testExternalViewUpdates > org.apache.helix.integration.TestEnableCompression.testEnableCompressionResource > org.apache.helix.integration.TestSchedulerMessage.testSchedulerMsg3 > org.apache.helix.integration.TestSchedulerMessage.testSchedulerMsg4 > org.apache.helix.integration.TestSchedulerMessage.testSchedulerMsgContraints > org.apache.helix.integration.TestSchedulerMessage.testSchedulerMsgUsingQueue > > I got these from my local build too. (mvn clean install package on > helix-0.6.x) > > > > Thanks > Lei > > -- > > Lei Xia > Software Engineer > Data Infrastructure/Distributed Data Systems/Nuage > LinkedIn > > [email protected] > www.linkedin.com/in/lxia1 > > ________________________________________ > From: kishore g [[email protected]] > Sent: Wednesday, March 11, 2015 2:03 PM > To: [email protected] > Cc: [email protected] > Subject: Re: Cutting a release 0.6.5 tonight > > Hi Lei, > > Can you point to the failures? > > thanks, > Kishore G > > On Wed, Mar 11, 2015 at 1:19 PM, Lei Xia <[email protected]> wrote: > >> Hi, Kishore >> >> I saw there are regression test failures from last two recent commits >> on 0.6.x branch, running from both local box and Linkedin's hudson jobs. >> Are we going to fix them before the release? >> >> >> Thanks >> Lei >> >> -- >> >> Lei Xia >> Software Engineer >> Data Infrastructure/Distributed Data Systems/Nuage >> LinkedIn >> >> [email protected] >> www.linkedin.com/in/lxia1 >> >> ________________________________________ >> From: kishore g [[email protected]] >> Sent: Wednesday, March 11, 2015 12:04 PM >> To: [email protected] >> Cc: [email protected] >> Subject: Re: Cutting a release 0.6.5 tonight >> >> Will write a test case for migration and document the steps >> On Mar 11, 2015 11:37 AM, "Varun Sharma" <[email protected]> wrote: >> >>> What would be the migration path from non-compressed buckets to >> compressed >>> non bucket resources ? It seems even the CURRENTSTATES are being bucketed >>> in this case, I thought that was not expected with bucketing. Does the >>> controller read these current states appropriately ? To migrate, it seems >>> that we would need to also rewrite the CURRENT STATES ? >>> >>> On Wed, Mar 11, 2015 at 10:02 AM, kishore g <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I will work with Jason to cut a 0.6.5 release tonight. >>>> >>>> The new thing I added is to enableCompression while storing data in >>>> Zookeeper, this allows us to go up to 100k partitions per resource >> without >>>> having to use bucketing feature. We also fixed few bugs with bucketed >>>> resource just in case some one needs it. >>>> >>>> The property store api needs some changes, I plan to get it in today. >>>> >>>> Let me know if you need any other changes to be included. Are there any >>>> changes that went into 0.7.x branch that we need to merge it back in to >>>> 0.6.x ? >>>> >>>> thanks, >>>> Kishore G >>>> >>>> >>>> >>>> >>>> >>>> >>> >>
