You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2015/05/11 22:55:00 UTC

[jira] [Updated] (PIG-4481) e2e tests ComputeSpec_1, ComputeSpec_2, StreamingPerformance_3 and StreamingPerformance_4 produce different result on Windows

     [ https://issues.apache.org/jira/browse/PIG-4481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Dai updated PIG-4481:
----------------------------
    Summary: e2e tests ComputeSpec_1, ComputeSpec_2, StreamingPerformance_3 and StreamingPerformance_4 produce different result on Windows  (was: e2e tests ComputeSpec_1, ComputeSpec_2 produce different result on Windows)

> e2e tests ComputeSpec_1, ComputeSpec_2, StreamingPerformance_3 and StreamingPerformance_4 produce different result on Windows
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-4481
>                 URL: https://issues.apache.org/jira/browse/PIG-4481
>             Project: Pig
>          Issue Type: Bug
>          Components: e2e harness
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>              Labels: windows
>             Fix For: 0.15.0
>
>         Attachments: PIG-4481-1.patch, PIG-4481-2.patch, PIG-4481-3.patch, PIG-4481-4.patch
>
>
> ComputeSpec_1, ComputeSpec_2, StreamingPerformance_3 and StreamingPerformance_4 produce the wrong result on Windows. Since Pig compare the test result with old version of Pig, which also produce wrong result, the test still pass.
> The cause of the issue is the parameter passing under Windows. Some parameter of executable cannot pass correctly on Windows. StreamingPerformance_3, StreamingPerformance_4 requires a simple quoting change and command line change. However, I didn't find a proper way to fix ComputeSpec_1 and ComputeSpec_2 as FS and OFS parameters could not be passed correctly to awk. Changing the test slightly to get around (not changing the intention of the test).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)