[
https://issues.apache.org/jira/browse/PIG-4759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141511#comment-15141511
]
Rohini Palaniswamy edited comment on PIG-4759 at 2/10/16 7:43 PM:
------------------------------------------------------------------
We need to that as that is the expected functionality. Else it is breaking
scripts and is backward incompatible with mapreduce.
Do not want to special case for same loader and try to match field names.
[~knoguchi] had a case where there was a static variable issue with one of the
native libraries and he had used load and store to separate it into multiple
jobs. Also these cases are rare enough it is not worth optimizing. Even if
multiple DAG, it reuses same application and containers. So not too much of a
cost.
was (Author: rohini):
We need to that as that is the expected functionality. Else it is breaking
scripts.
> Fix Classresolution_1 e2e failure
> ---------------------------------
>
> Key: PIG-4759
> URL: https://issues.apache.org/jira/browse/PIG-4759
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.16.0
>
> Attachments: PIG-4759-1.patch
>
>
> We had left it as a known issue to be fixed later as that was a very odd
> and uncommon usage put in just for the particular testcase - store into a
> file with one StoreFunc, but read back with a different reader in the same
> script. But came across one of our user doing that same case. Storing bags
> using PigStorage and reading back with TextLoader and processing them as
> plain strings later on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
