hadoop-pig-dev mailing list archives

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

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

Alan Gates commented on PIG-734:

I wasn't planning on making mymap#1 translate to mymap#'1'.  The issue I see with that is
if that works, why doesn't mymap#intcol work?  I'm concerned that sayings keys need to be
strings but then cheating in this one case will make the semantics confusing.

> 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