[
https://issues.apache.org/jira/browse/HADOOP-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16564591#comment-16564591
]
Steve Loughran commented on HADOOP-15645:
-----------------------------------------
Patch 001
* better setup of {{AbstractS3GuardToolTestBase}} implementations, especially
bucket config, where per-bucket settings are cleared
* {{ITestS3GuardToolDynamoDB}} and {{ITestS3GuardToolLocal}} both check the
metastore type of the test FS, skip if not correct -and include details on
store in the message.
* testDiff test erases test FS in testDiff setup through rawFS and metastore
FS, in case it gets contaminated
This addresses the double setup of dynamodb being picked up on a local test
run, the ddb metastore getting tainted with stuff which shouldn't be there, and
the s3 bucket getting stuff into it which the getFileSystem() fs doesn't
see/delete.
> ITestS3GuardToolLocal.testDiffCommand fails if bucket has per-bucket binding
> to DDB
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-15645
> URL: https://issues.apache.org/jira/browse/HADOOP-15645
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.0
> Reporter: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-15645-001.patch
>
>
> If your bucket has a per-bucket setting to use S3Guard, then the
> ITestS3GuardToolLocal.testDiffCommand test can fail as fs-only data can creep
> into the metastore.
> The rawfs should use clearBucketOption to clear the metastore binding, so
> guarantee a real raw fs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
