pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-2484) Fix several e2e test failures/aborts for 23
Date Fri, 20 Jan 2012 23:40:39 GMT

    [ https://issues.apache.org/jira/browse/PIG-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190197#comment-13190197
] 

Thejas M Nair commented on PIG-2484:
------------------------------------

+1
The 23 specific test case parameters are very useful. We know what to revisit later (ignore23
etc).
I think we should see if the " register './python/scriptingudf.py'.. " use case would work
with hadoop 23 if pig removes the "./" prefix. Opened PIG-2486 to track that.

                
> Fix several e2e test failures/aborts for 23
> -------------------------------------------
>
>                 Key: PIG-2484
>                 URL: https://issues.apache.org/jira/browse/PIG-2484
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>    Affects Versions: 0.9.2, 0.10, 0.11
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.10, 0.9.3, 0.11
>
>         Attachments: PIG-2484-1.patch, PIG-2484-2.patch, PIG-2484-3.patch
>
>
> There are still a couple of e2e test aborts/failures for hadoop23. Most of them are due
to test infrastructure, minor backward incompatibility change in 23, or recent changes in
Pig. Here is a list:
> Scripting_1/Scripting_2: MAPREDUCE-3700
> Native_3: 23 test need a hadoop23-steaming.jar
> MonitoredUDF_1: Seems related to guava upgrade (PIG-2460), Pig's guava is newer than
hadoop23's
> UdfException_1, UdfException_2, UdfException_3, UdfException_4: Error message change
> Checkin_2, GroupAggFunc_7, GroupAggFunc_9, GroupAggFunc_12, GroupAggFunc_13, Types_6,
Scalar_1: float precision
> Limit_2: The specific output records change, test infrastructure should allow this

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message