[
https://issues.apache.org/jira/browse/PIG-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates updated PIG-734:
---------------------------
Attachment: PIG-734_3.patch
Attaching a version of the file that fixes some of the introduced compiler
warnings. The findbugs warnings have to do with naming convention. All of the
function names in QueryParser start with upper case, so I am only following the
convention there.
> 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.4.0
>
> Attachments: PIG-734.patch, PIG-734_2.patch, PIG-734_3.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.
