hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabor Bota (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HADOOP-15511) ITestS3GuardListConsistency#testRollingRenames bad parameters passed to doTestRenameSequence
Date Mon, 04 Jun 2018 14:50:00 GMT

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

Gabor Bota resolved HADOOP-15511.
---------------------------------
    Resolution: Not A Problem

Sorry for the noise on this, as it turns out the test is working as expected.

The following happens:
   * Tests a circular sequence of renames to verify that overwriting recently
   * deleted files and reading recently created files from rename operations
   * works as expected.
The first check of the directory (the first doTestRenameSequence)  won't check anything, but
the followups are working as expected.

> ITestS3GuardListConsistency#testRollingRenames bad parameters passed to doTestRenameSequence
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-15511
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15511
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 3.1.0
>            Reporter: Gabor Bota
>            Assignee: Gabor Bota
>            Priority: Major
>
> Bumped into this while working on HADOOP-15423.
> Currently the parameters passed to doTestRenameSequence are the following:
> {noformat}
> mkdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> mkdirs: {}
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> mkdirs: {}
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> mkdirs: {}
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> mkdirs: {}
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> mkdirs: {}
> srcdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/1
> dstdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> yesdirs: s3a://cloudera-dev-gabor-ireland/test/rolling/2
> nodirs: s3a://cloudera-dev-gabor-ireland/test/rolling/3
> {noformat}
> The problem is that we should check that the srcdir is moved to dstdirs, so it should
be check in nodirs. Right now nodirs parameter checks for directories which are completely
unrelated to the cases, so this part of the test should be fixed to check for dirs that are
related to the cases. Basically the nodirs should be equal to srcdirs in this case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message