[
https://issues.apache.org/jira/browse/PIG-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879313#comment-15879313
]
Koji Noguchi commented on PIG-5153:
-----------------------------------
Before, I believe it was just no-op for FLATTEN(map).
Given this is a change in behavior, can [~daijy]/[~rohini] +1 for keeping the
new behavior?
Then, I think the only thing to do is,
* Modify testcase
* Move CHANGES.txt for PIG-5085 to INCOMPATIBLE CHANGES and also set the flag
on the jira.
> Change of behavior in FLATTEN(map)
> ----------------------------------
>
> Key: PIG-5153
> URL: https://issues.apache.org/jira/browse/PIG-5153
> Project: Pig
> Issue Type: Test
> Reporter: Koji Noguchi
> Priority: Minor
>
> In PIG-5085 we changed the behavior of FLATTEN on map.
> (I didn't even know this was even allowed until I saw the following test
> failure.)
> e2e nightly FOREACH_6 started failing after this change.
> {code}
> 'num' => 6,
> 'pig' => q\register :FUNCPATH:/testudf.jar;
> a = load ':INPATH:/singlefile/studenttab10k' as (name, age, gpa);
> b = foreach a generate flatten(name) as n,
> flatten(org.apache.pig.test.udf.evalfunc.CreateMap((chararray)name, gpa)) as
> m;
> store b into ':OUTPATH:' using
> org.apache.pig.test.udf.storefunc.StringStore();\,
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
