I will do it tomorrow on one of my workflows. Could take some trial and error to get it working.
-- Joe On Apr 23, 2012, at 6:53 PM, Russell Jurney <[email protected]> wrote: > Can someone from LinkedIn try this release candidate? It may break > your AvroStorage, so that would be good to know. > > Russell Jurney http://datasyndrome.com > > On Apr 23, 2012, at 6:36 PM, Dmitriy Ryaboy <[email protected]> wrote: > >> +1 >> >> >> Verified several jobs using Elephant-Bird loaders. >> Tested correctness with pig.exec.mapPartAgg both true and false. >> Verified license. >> Verified release notes. >> Ran test-commit >> >> D >> >> On Sat, Apr 21, 2012 at 12:27 PM, Daniel Dai <[email protected]> wrote: >>> We should do sanity check of the package, such as unit tests, e2e >>> tests, piggybank tests, package integrity, package signature, license, >>> etc. However, if we find a new bug, usually we will push it to the >>> next release at this stage unless it is a critical one. >>> >>> Thanks, >>> Daniel >>> >>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi >>> <[email protected]> wrote: >>>> Hi Daniel, >>>> >>>> What is required other than running the regular tests for testing release >>>> candidate? I can think of running a few existing scripts against candidate >>>> build and making sure outputs look fine. >>>> >>>> Thanks, >>>> Prashant >>>> >>>> On Fri, Apr 20, 2012 at 12:39 AM, Daniel Dai <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> I have created a candidate build for Pig 0.10.0. >>>>> >>>>> Keys used to sign the release are available at >>>>> http://svn.apache.org/viewvc/pig/trunk/KEYS?view=markup. >>>>> >>>>> Please download, test, and try it out: >>>>> >>>>> http://people.apache.org/~daijy/pig-0.10.0-candidate-0/ >>>>> >>>>> Should we release this? Vote closes on next Tuesday, Apr 24th. >>>>> >>>>> Daniel >>>>>
