[ 
https://issues.apache.org/jira/browse/HADOOP-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607131#comment-15607131
 ] 

Manoj Govindassamy commented on HADOOP-8299:
--------------------------------------------

Thats true, HADOOP-13055 is under code review and might not be in before this. 
So, attaching v02 patch with unsupported message for LinkMergeSlash and the 
test case modified accordingly. Thanks for the review.

> 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: 3.0.0-alpha1
>            Reporter: Eli Collins
>            Assignee: Manoj Govindassamy
>         Attachments: HADOOP-8299.01.patch, HADOOP-8299.02.patch
>
>
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to