[
https://issues.apache.org/jira/browse/PIG-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547085#comment-13547085
]
Alan Gates commented on PIG-2769:
---------------------------------
When I do a clean first as Cheolsoo advises it works, though I don't fully
understand that since I started out with a clean checkout.
In the system tests NegForeach_7, NegForeach_9, SyntaxErrors_4, Macro_Error_4
all fail because the error messages have changed. You can find these in
test/e2e/pig/tests/negative.conf and macro.conf. Search on each of the group
names (NegForeach, ...) and then find the test number under that. In each case
you can run the query and change the expected error message to match the new
one.
Other than that, +1, patch looks good.
> a simple logic causes very long compiling time on pig 0.10.0
> ------------------------------------------------------------
>
> Key: PIG-2769
> URL: https://issues.apache.org/jira/browse/PIG-2769
> Project: Pig
> Issue Type: Bug
> Components: build
> Affects Versions: 0.10.0
> Environment: Apache Pig version 0.10.0-SNAPSHOT (rexported)
> Reporter: Dan Li
> Assignee: Nick White
> Fix For: 0.12
>
> Attachments: case1.tar, PIG-2769.0.patch,
> TEST-org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.TestInputSizeReducerEstimator.txt
>
>
> We found the following simple logic will cause very long compiling time for
> pig 0.10.0, while using pig 0.8.1, everything is fine.
> A = load 'A.txt' using PigStorage() AS (m: int);
> B = FOREACH A {
> days_str = (chararray)
> (m == 1 ? 31:
> (m == 2 ? 28:
> (m == 3 ? 31:
> (m == 4 ? 30:
> (m == 5 ? 31:
> (m == 6 ? 30:
> (m == 7 ? 31:
> (m == 8 ? 31:
> (m == 9 ? 30:
> (m == 10 ? 31:
> (m == 11 ? 30:31)))))))))));
> GENERATE
> days_str as days_str;
> }
> store B into 'B';
> and here's a simple input file example: A.txt
> 1
> 2
> 3
> The pig version we used in the test
> Apache Pig version 0.10.0-SNAPSHOT (rexported)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
