[
https://issues.apache.org/jira/browse/PIG-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828231#comment-15828231
]
Adam Szita commented on PIG-5110:
---------------------------------
Obviously this can be worked around with FOREACH operators and specifying
custom alias names for small relations, but for those with lot of fields or
where we don't know the field name this is not an option.
Possible solutions that pop into my mind are:
-Introducing a Pig property to disable the feature, and hooking the
configuration to the relevant operators so that they know if prepending with ::
is required or not
e.g. in
https://github.com/apache/pig/blob/trunk/src/org/apache/pig/newplan/logical/relational/LOJoin.java#L150
we can enhance the condition according to what our new property is set to.
-Expanding the query language by introducing a new operator just for this
purpose - this could be used just before STORE or DUMP operators to fix alias
names.
[~rohini] what's your opinion?
> Removing schema alias and :: coming from parent relation
> --------------------------------------------------------
>
> Key: PIG-5110
> URL: https://issues.apache.org/jira/browse/PIG-5110
> Project: Pig
> Issue Type: New Feature
> Reporter: Adam Szita
> Assignee: Adam Szita
>
> Customers have asked for a feature to get rid of the schema alias prefixes.
> CROSS, JOIN, FLATTEN, etc.. prepend the field name with the parent field
> alias and ::
> I would like to find a way to disable this feature. (The burden of making
> sure not to have duplicate aliases - and hence the appropriate
> FrontendException getting thrown - is on the user)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
