You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/03/26 00:35:00 UTC

[jira] [Commented] (MAPREDUCE-7524) testSplitPlacementForCompressedFiles is non-deterministic from time to time

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

ASF GitHub Bot commented on MAPREDUCE-7524:
-------------------------------------------

github-actions[bot] commented on PR #8134:
URL: https://github.com/apache/hadoop/pull/8134#issuecomment-4130738829

   We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
   Thanks all for your contribution.




> testSplitPlacementForCompressedFiles is non-deterministic from time to time
> ---------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-7524
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7524
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>            Reporter: Paco Chan
>            Priority: Trivial
>              Labels: pull-request-available
>
> {code:java}
> org.apache.hadoop.mapreduce.lib.input.TestCombineFileInputFormat.testSplitPlacementForCompressedFiles{code}
>  makes a number of assertions that are not guaranteed by internal implementation.
>  
> For example, the test makes assumptions on the order in which racks are processed. Splits in the HDFS can appear in a different order depending on the internal state / implementation / metadata which is not guaranteed by the interface.
>  
> For example, there are assertions such as split.equals(splits.get(0)), which assumes a specific ordering of InputSplit objects that may vary depending on internal implementation. 
>  
> This can be addressed by eliminating assertions based on the internal implementation / ways that the racks are split. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org