Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -1492,7 +1492,7 @@ public boolean hasMetadataStore() {
* is set for this filesystem.
*/
@VisibleForTesting
boolean hasAuthoritativeMetadataStore() {
public boolean hasAuthoritativeMetadataStore() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now this is done on a per path basis is this probe adequate?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is used in org.apache.hadoop.fs.s3a.s3guard.ITestS3GuardFsck#testIAuthoritativeDirectoryContentMismatch and I think that's the easiest to check in runtime. But I can use something else like getting it from the fs's config.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If someone has configured the test path to be authoritative, then even if the store says non-auth you'll get auth-store-behaviours. Best to either unset the per-bucket/global auth mode settings in test config creation or check the auth mode of the actual test path.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we're only using this for tests, so I'm not as worried as I was. +1 for this change

return hasMetadataStore() && allowAuthoritativeMetadataStore;
}

Expand Down
Loading