[
https://issues.apache.org/jira/browse/PIG-3790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922969#comment-13922969
]
Rohini Palaniswamy commented on PIG-3790:
-----------------------------------------
I am noticing that even when specifying -Dharness.old.pig pointing to a older
version, the benchmark is still being run with the compiled pig.jar and
Multiquery benchmarks fail because of that. I would expect the benchmarks to be
run with pig libraries from -Dharness.old.pig setting. This needs to be
investigated.
> Several changes in Tez e2e
> --------------------------
>
> Key: PIG-3790
> URL: https://issues.apache.org/jira/browse/PIG-3790
> Project: Pig
> Issue Type: Sub-task
> Components: tez
> Affects Versions: tez-branch
> Reporter: Daniel Dai
> Assignee: Daniel Dai
> Fix For: tez-branch
>
> Attachments: PIG-3790-1.patch
>
>
> Need to change several thing in e2e:
> 1. If test contains tag "verify_pig_script", "verify_pig_script" still run
> against tez, should run against MR
> 2. Have the following line in test:
> $ENV{'PIG_CLASSPATH'} = $ENV{'PIG_CLASSPATH'} . $separator . $pcp;
> PIG_CLASSPATH eventually get too long and exceed system limit
> 3. Some tests such as MultiQuery_11, perl command is enclosed in double quote
> (perl -ne "print $_;"), Pig runtime will do the parameter substitution and
> replace $_ to the last command executed. This seems should goes to MR as
> well, if so, I will open another ticket to fix in trunk.
> 4. Since e2e is now in a good shape, we need to enable all test suite instead
> of just tez.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
