Skip to content

HADOOP-18802. Collision of config key name fs.viewfs.mounttable.default.name.key to other keys that specify the entry point to mount tables #6040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

HADOOP-18802. Collision of config key name fs.viewfs.mounttable.default.name.key to other keys that specify the entry point to mount tables #6040

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/viewfs/Constants.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ public interface Constants {
* Config key to specify the name of the default mount table.
*/
String CONFIG_VIEWFS_DEFAULT_MOUNT_TABLE_NAME_KEY =
"fs.viewfs.mounttable.default.name.key";
"fs.viewfs.mounttable.default-name-key";

/**
* Config variable name for the default mount table.
Expand Down
4 changes: 2 additions & 2 deletions hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/ViewFsOverloadScheme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,10 +179,10 @@ For example, when the following configuration is used but a path like `viewfs:/f
```

### Solution
To avoid the above problem, the configuration `fs.viewfs.mounttable.default.name.key` has to be set to the name of the cluster, i.e, the following should be added to `core-site.xml`
To avoid the above problem, the configuration `fs.viewfs.mounttable.default-name-key` has to be set to the name of the cluster, i.e, the following should be added to `core-site.xml`
```xml
<property>
<name>fs.viewfs.mounttable.default.name.key</name>
<name>fs.viewfs.mounttable.default-name-key</name>
<value>cluster</value>
</property>
```
Expand Down