hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Ciemiewicz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-734) Non-string keys in maps
Date Fri, 08 May 2009 15:31:45 GMT

    [ https://issues.apache.org/jira/browse/PIG-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707377#action_12707377

David Ciemiewicz commented on PIG-734:

Alan, if I don't think this is going to be that problematic.

Even if I try to pass in a map dereference with an integer such as mymap#1, would pig automagically
convert the 1 to a string equivalent to mymap#'1'.  If so, I think this would be quite acceptable.

> Non-string keys in maps
> -----------------------
>                 Key: PIG-734
>                 URL: https://issues.apache.org/jira/browse/PIG-734
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>            Priority: Minor
>             Fix For: 0.3.0
>         Attachments: PIG-734.patch
> With the addition of types to pig, maps were changed to allow any atomic type to be a
key.  However, in practice we do not see people using keys other than strings.  And allowing
multiple types is causing us issues in serializing data (we have to check what every key type
is) and in the design for non-java UDFs (since many scripting languages include associative
arrays such as Perl's hash).
> So I propose we scope back maps to only have string keys.  This would be a non-compatible
change.  But I am not aware of anyone using non-string keys, so hopefully it would have little
or no impact.

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

View raw message