[
https://issues.apache.org/jira/browse/HADOOP-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manoj Govindassamy updated HADOOP-8299:
---------------------------------------
Target Version/s: 3.0.0-alpha2 (was: 2.0.0-alpha)
Summary: ViewFileSystem link slash mount point crashes with
IndexOutOfBoundsException (was: ViewFs doesn't work with a slash mount point)
ViewFileSystem support for LinkMergeSlash is now tracked by HADOOP-13055.
Will make use of this bug to address the issue discussed in the previous
comment -- "link./" mount point throwing IndexOutOfBoundsException.
> ViewFileSystem link slash mount point crashes with IndexOutOfBoundsException
> ----------------------------------------------------------------------------
>
> Key: HADOOP-8299
> URL: https://issues.apache.org/jira/browse/HADOOP-8299
> Project: Hadoop Common
> Issue Type: Bug
> Components: viewfs
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Assignee: Manoj Govindassamy
>
> We currently assume [a typical viewfs client
> configuration|https://issues.apache.org/jira/secure/attachment/12507504/viewfs_TypicalMountTable.png]
> is a set of non-overlapping mounts. This means every time you want to add a
> new top-level directory you need to update the client-side mountable config.
> If users could specify a slash mount, and then add additional mounts as
> necessary they could add a new top-level directory without updating all
> client configs (as long as the new top-level directory was being created on
> the NN the slash mount points to). This could be achieved by HADOOP-8298
> (merge mounts, since we're effectively merging all new mount points with
> slash) or having the notion of a "default NN" for a mount table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
