[
https://issues.apache.org/jira/browse/PIG-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117131#comment-16117131
]
Rohini Palaniswamy commented on PIG-5286:
-----------------------------------------
bq. Then we need separate e2e test that simply run old-pig and current?
Don't think so. Don't see a reason to have verify_pig run with same version.
We usually use verify_pig when there is new code and the verify_pig script
written is usually compatible with previous versions. It may only become a
problem if one goes to a very old release. Considering that it can cause bugs
to go unnoticed, I don't think we should be running verify_pig with the current
version.
> Run verify_pig in e2e with old version of Pig
> ---------------------------------------------
>
> Key: PIG-5286
> URL: https://issues.apache.org/jira/browse/PIG-5286
> Project: Pig
> Issue Type: Bug
> Reporter: Rohini Palaniswamy
> Assignee: Rohini Palaniswamy
> Fix For: 0.18.0
>
> Attachments: PIG-5286-1.patch
>
>
> Currently verify_pig runs a different equivalent script as the testcase but
> runs with the same version of Pig. Ran into a issue where a test passed when
> a bug was introduced and benchmark files were not present. The newly
> generated benchmarks were also wrong. Caught the failure when running again
> pointing to previously generated benchmarks.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
