hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kay Kay (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1334) contrib/index - test - TestIndexUpdater fails due to an additional presence of file _SUCCESS in hdfs
Date Tue, 29 Dec 2009 19:01:29 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795105#action_12795105

Kay Kay commented on MAPREDUCE-1334:

This bug ( due to the presence of an extra file , _SUCCESS ) seems to be an artifact of MAPREDUCE-947

May be - trying with FileOutputCommitter.SUCCESSFUL_JOB_OUTPUT_DIR_MARKER to false in Configuration
might help. 

> contrib/index - test - TestIndexUpdater fails due to an additional presence of file _SUCCESS
in hdfs 
> -----------------------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-1334
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1334
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Kay Kay
>             Fix For: 0.21.0
>         Attachments: MAPREDUCE-1334.patch
> $ cd src/contrib/index
> $ ant clean test 
> This fails the test TestIndexUpdater due to a mismatch in the - doneFileNames - data
structure, when it is being run with different parameters. 
> (ArrayIndexOutOfBoundsException raised when inserting elements in doneFileNames, array
> Debugging further - there seems to be an additional file called as - hdfs://localhost:36021/myoutput/_SUCCESS
, taken into consideration in addition to those that begins with done* .  The presence of
the extra file causes the error. 
> Attaching a patch that would circumvent this by increasing the array length of shards
by 1 . 
> But longer term the test fixtures need to be probably revisited to see if the presence
of _SUCCESS as a file is a good thing to begin with before we even get to this test case.

> Any comments / suggestions on the same welcome. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message