[ 
https://issues.apache.org/jira/browse/PIG-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774176#action_12774176
 ] 

Dmitriy V. Ryaboy commented on PIG-1016:
----------------------------------------

HC Busy,
The decision making process should be explained somewhere on the apache process 
pages, but essentially -- there is a group of committers, who are final 
arbiters in what gets in and what doesn't. There's about 10 of them right now I 
think (Thejas, Alan, Daniel, and Santosh are all committers -- you are getting 
a fair bit of attention! :-)).  Patches go in when one of the committers gives 
a patch a "+1" vote, unless of course it's the committer's own patch -- then a 
different committer has to approve it.

The trouble with modifying PigStorage is that it's the default storage 
interpreter, so all changes have to be really thought through for it, and the 
preference is for doing the safe thing over the convenient thing.  So the bar 
is pretty high for that.  The change that reduced the functionality did so 
because this functionality was broken... so it won't be reversed until it's not 
broken.  

All that being said, I've found the committers to be perceptive to reasonable 
arguments. So you have two options -- change your patch to a 
TypedMapPigStorage, and put it in piggybank (that will probably get in quite 
fast), or continue working with the committers on finding a solution that works 
to their standards.

-D

> Reading in map data seems broken
> --------------------------------
>
>                 Key: PIG-1016
>                 URL: https://issues.apache.org/jira/browse/PIG-1016
>             Project: Pig
>          Issue Type: Improvement
>          Components: data
>    Affects Versions: 0.4.0
>            Reporter: hc busy
>             Fix For: 0.5.0
>
>         Attachments: PIG-1016.patch
>
>
> Hi, I'm trying to load a map that has a tuple for value. The read fails in 
> 0.4.0 because of a misconfiguration in the parser. Where as in almost all 
> documentation it is stated that value of the map can be any time.
> I've attached a patch that allows us to read in complex objects as value as 
> documented. I've done simple verification of loading in maps with tuple/map 
> values and writing them back out using LOAD and STORE. All seems to work fine.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to