PIG-2889 is 0.12, maybe wontfix.
PIG-2927 is jco's patch. We can't figure a way to unit test, but three
of us have tested it. Can we get a pass on a test, or can someone
chime in with how to test?
PIG-2614 is also jco's patch. I don't think the first pass worked, so
this is 0.12. Ask jco to confirm.
PIG-2939 is 0.12
PIG-2830 is 0.12
PIG-2641 - code in UDF form is here:
https://github.com/rjurney/pig-to-json but should be updated to trunk
APIs. Someone tell me if I should make a go at getting this a builtin
in 0.11.
PIG-2631 is a good idea and is jco's but there's no patch. 0.12?

Russell Jurney twitter.com/rjurney


On Oct 28, 2012, at 4:01 PM, Rohini Palaniswamy <rohini.adi...@gmail.com> wrote:

> Hi all,
>    Tried to take a look at the jira's Olga mentioned. Thought it would be
> easier to compile a list instead of reviewing and commenting on each jira.
> Here is a initial list that I compiled as a kick starter for the
> discussions.
>
> Query used:
> https://issues.apache.org/jira/secure/IssueNavigator!executeAdvanced.jspa
>
> project = PIG AND fixVersion in ("0.11") AND (status = open OR status =
> "patch available") ORDER BY status DESC, key DESC
>
>
> Jiras for 0.11:
> * PIG-2972 and its subtasks - Umbrella ticket for test failures in
> 0.11/trunk
> * PIG-2793 and its subtasks - Make Pig Work on Windows without Cygwin
> * PIG-2756 - Documentation for 0.11
> * PIG-2980 - documentation for DateTime datatype
> * PIG-2996 - The buildtin function "ToDate" has been mapped with wrong
> class names
>        * PIG-2982 - add unit tests for DateTime type that test setting
> timezone
> * PIG-2907 - Publish pig 0.23 jars to maven
> * PIG-2898 - Parallel execution of e2e tests  ( I want this badly in :))
>        * PIG-2927 - SHIP and use JRuby gems in JRuby UDFs (Russell
> requested for this in 0.11)
> Confirmation based on Owner/Reporter ??:
>    * PIG-2981 - add e2e tests for DateTime data type (Thejas)
>    * PIG-2815 - class loader management in PigContext (Raghu Angadi)
>    * PIG-2812 - Spill InternalCachedBag into only 1 file (Haitao Yao)
>    * PIG-2767 - Pig creates wrong schema after dereferencing nested tuple
> fields (Daniel Dai/Jonathan Packer)
>    * PIG-2614 - AvroStorage crashes on LOADING a single bad error
> (Jonathan Coveney/Russell Jurney)
>    * PIG-2537 - Output from flatten with a null tuple input generating
> data inconsistent with the schema (Daniel Dai/Xuefu Zhang)
>    * PIG-1967 - deprecate current syntax for casting relation as scalar,
> to use explicit cast to tuple (Thejas)
>    * PIG-1919 - order-by on bag gives error only at runtime (Thejas)
> Candidates for moving to 0.12:
>    * PIG-2937 - generated field in nested foreach does not inherit the
> variable name as the field name
>    * PIG-2834 - MultiStorage requires unused constructor argument
>    * PIG-2657 - Print warning if using wrong jython version
>    * PIG-2362 - Rework Ant build.xml to use macrodef instead of antcall
>    * PIG-2312 - NPE when relation and column share the same name and used
> in Nested Foreach
>    * PIG-2997 - Provide a convenience constructor on PigServer that
> accepts Configuration
>    * PIG-2939 - Pig macros need namespaces to avoid namespace collisions
> facilitate macro sharing
>    * PIG-2889 - HBaseAvroStorage UDF
>    * PIG-2830 - Macros should work in Grunt
>    * PIG-2687 - Add relation/operator scoping to Pig
>    * PIG-2681 - TestDriverPig.countStores() does not correctly count the
> number of stores for pig scripts using variables for the alias
>    * PIG-2674 - Document how parameter values that contain spaces can be
> passed to Pig
>    * PIG-2643 - Use bytecode generation to make a performance replacement
> for InvokeForLong, InvokeForString, etc
>    * PIG-2641 - Create toJSON function for all complex types: tuples, bags
> and maps
>    * PIG-2633 - Create a SchemaBag which generates a Bag with a known
> Schema via code gen
>    * PIG-2631 - Pig should allow self joins
>    * PIG-2630 - Issue with setting "b = a;"
>    * PIG-2628 - Allow in line scripting UDF definitions
>    * PIG-2625 - Allow use of JRuby for control flow
>    * PIG-2624 - Handle recursive inclusion of scripts in JRuby UDFs
>    * PIG-2595 - BinCond only works inside parentheses
>    * PIG-2591 - Unit tests should not write to /tmp but respect
> java.io.tmpdir
>    * PIG-2584 - Command line arguments for Pig script
>     * PIG-2552 - Better Property handling to deal with deprecation and
> variable substitution of Hadoop config
>    * PIG-2522 - deprecated hdfs pig commands do not work well with client
> side tables
>    * PIG-2521 - explicit reference to namenode path with streaming results
> in an error
>    * PIG-2461 - Simplify schema syntax for cast
>    * PIG-2446 - Fix map input bytes for hadoop 20.203+
>    * PIG-2434 - investigate 5% slowdown in TPC-H Q6 query in 0.10
>    * PIG-2424 - Add OUTER_FLATTEN operator which, on an empty bag, returns
> null instead of throwing away the row
>    * PIG-2423 - document use case where co-group is better choice than join
>    * PIG-2416 - 23 local mode enter into infinite loop if mapred-site.xml
> in classpath
>    * PIG-2409 - Tracking URL for hadoop 23 does not show up
>    * PIG-2407 - Clean up warning messages for hadoop 23
>
> Regards,
> Rohini
>
> On Fri, Oct 26, 2012 at 4:32 PM, Olga Natkovich <onatkov...@yahoo.com>wrote:
>
>> 74 issues still open and more than half unassigned. I think we should
>> narrow list down next week. I am planning to start unlinking the unassigned
>> ones next week so if you feel they need to be addressed, please, find owner.
>>
>> Olga
>>
>>
>>
>> ----- Original Message -----
>> From: Olga Natkovich <onatkov...@yahoo.com>
>> To: "dev@pig.apache.org" <dev@pig.apache.org>
>> Cc:
>> Sent: Monday, October 22, 2012 10:14 AM
>> Subject: Re: Pig 0.11
>>
>> There are still 76 unresolved JIRAs more than half unassigned. Lets clean
>> this up by theend of this week. I propose we do the following:
>>
>> (1) Unlink all JIRAs for new features since we already branched so we
>> should not be taken on new work. If people feel strongly that some new
>> features still need to go in please bring it up.
>> (2) For bug fixes, if people fill strongly that some of the unassigned
>> issues need to be addressed please take ownership. If you are unable to
>> solve them but still feel they are important, please, bring them up.
>> (3) Owners of unresolved issues, please, take a look if you will have time
>> to solve them in the next 2 weeks. If not, lets move them to 12. If you
>> can't address them but feel they are important, please, bring it up.
>>
>> Lets make sure that all JIRAs that require changes to the documentation
>> have appropriate information in the release notes section so that we can
>> quickly compile release documentation.
>>
>> Thanks for you help!
>>
>> Olga
>>
>>
>>
>>
>> ________________________________
>> From: Alan Gates <ga...@hortonworks.com>
>> To: dev@pig.apache.org
>> Sent: Monday, October 15, 2012 11:55 AM
>> Subject: Re: Pig 0.11
>>
>> At this point no one has taken on release documentation for 0.11.
>>
>> Alan.
>>
>> On Oct 15, 2012, at 11:49 AM, Olga Natkovich wrote:
>>
>>> Thanks!
>>>
>>> Are you talking about items 15 and 16 on the How To Release.Publish
>> page?
>>>
>>> Also, who is doing release documentation these days? I can help with
>> that as well. I would also be happy to roll the release if you guys need
>> help with that.
>>>
>>> Olga
>>>
>>>
>>> ________________________________
>>> From: Dmitriy Ryaboy <dvrya...@gmail.com>
>>> To: "dev@pig.apache.org" <dev@pig.apache.org>
>>> Cc: "dev@pig.apache.org" <dev@pig.apache.org>
>>> Sent: Friday, October 12, 2012 5:59 PM
>>> Subject: Re: Pig 0.11
>>>
>>> Thanks Olga and welcome back!
>>> I know there's some process for linking jiras to releases, but I'm not
>> sure what that is. If you could explain and maybe cover a portion of that
>> work, that'd be super helpful. And reviews, of course.
>>>
>>> On Oct 12, 2012, at 2:06 PM, Olga Natkovich <onatkov...@yahoo.com>
>> wrote:
>>>
>>>> Dmitry, I would be happy to help with the release process. Want to get
>> back into this now that I am back at work. Let me know what you would like
>> me to do.
>>>>
>>>> Olga
>>>>
>>>>
>>>>
>>>> ________________________________
>>>> From: Dmitriy Ryaboy <dvrya...@gmail.com>
>>>> To: dev@pig.apache.org
>>>> Cc: billgra...@gmail.com
>>>> Sent: Thursday, October 11, 2012 2:44 PM
>>>> Subject: Re: Pig 0.11
>>>>
>>>> Ok I will branch 0.11 tomorrow morning unless someone objects.
>>>> From then on, committers should be careful to commit bug fixes to both
>>>> 0.11 branch and trunk; minor polish can go into the branch, but whole
>>>> new features should not (we can discuss on the list if something is in
>>>> the gray area).
>>>>
>>>> D
>>>>
>>>> On Thu, Oct 11, 2012 at 2:16 PM, Gianmarco De Francisci Morales
>>>> <g...@apache.org> wrote:
>>>>> I added it as a dependency as it has already its own Jira.
>>>>> I hope it is OK.
>>>>>
>>>>> Cheers,
>>>>> --
>>>>> Gianmarco
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 10, 2012 at 11:23 PM, Bill Graham <billgra...@gmail.com>
>> wrote:
>>>>>
>>>>>> +1 for me.
>>>>>>
>>>>>> There's https://issues.apache.org/jira/browse/PIG-2756 which tracks
>> a few
>>>>>> documentation issues that should block Pig 0.11, but they can also be
>> done
>>>>>> on the trunk and merged to the branch. Gianmarco, you can add a rank
>>>>>> subtask there to serve as a reminder.
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 10, 2012 at 11:03 PM, Gianmarco De Francisci Morales <
>>>>>> g...@apache.org> wrote:
>>>>>>
>>>>>>> We are missing some documentation on the RANK but I guess we could
>> add
>>>>>> that
>>>>>>> to the branch and trunk in parallel.
>>>>>>> All the patches I was keeping an eye on are in.
>>>>>>>
>>>>>>> So +1 for me.
>>>>>>> --
>>>>>>> Gianmarco
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Oct 10, 2012 at 5:31 PM, Jonathan Coveney <
>> jcove...@gmail.com
>>>>>>>> wrote:
>>>>>>>
>>>>>>>> I think all of the major patches are in, no? Now it's just bug
>> testing?
>>>>>>>> Just wanted to touch base on where we are at with this.
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Note that I'm no longer using my Yahoo! email address. Please email
>> me at
>>>>>> billgra...@gmail.com going forward.*
>>
>>

Reply via email to