[
https://issues.apache.org/jira/browse/PIG-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839891#action_12839891
]
Alan Gates commented on PIG-1248:
---------------------------------
I agree camel case is easier on the eyes (and on the fingers). But we seem to
have chosen all caps for built in functions. Some of these we'll eventually
want to move into builtins for Pig. I really don't want to bring in builtins
that aren't all caps. For functions we think we might want to bring into
builtin someday it seems like it would be better to start them out in all caps
now rather than changing them later.
One other thought on the tuples via bags. If you have a script like:
{code}
A = load 'bla' using TextLoader();
B = foreach A generate flatten(Split($0));
{code}
Assume a file that contains : "Mary had a little lamb". If Split returns
tuples then B will return 1 record, "Mary had a little lamb". If Split returns
a bag, then B will generate 5 records ("Mary", "had", "a", "little", "lamb").
I don't have any guess of which of those users will want more.
> [piggybank] useful String functions
> -----------------------------------
>
> Key: PIG-1248
> URL: https://issues.apache.org/jira/browse/PIG-1248
> Project: Pig
> Issue Type: New Feature
> Reporter: Dmitriy V. Ryaboy
> Assignee: Dmitriy V. Ryaboy
> Fix For: 0.7.0
>
> Attachments: PIG_1248.diff, PIG_1248.diff, PIG_1248.diff
>
>
> Pig ships with very few evalFuncs for working with strings. This jira is for
> adding a few more.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
