[ 
https://issues.apache.org/jira/browse/HDFS-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colin Patrick McCabe updated HDFS-4019:
---------------------------------------

    Attachment: HDFS-4019.001.patch

* Add {{ln}} command to {{FSShell}}.

* {{FileContext#globStatus}} and {{FileSystem#globStatus}} should use 
{{getFileLinkStatus}} rather than {{getFileStatus}}.  Otherwise information 
about the paths are lost.

* The {{ls}} command should display something like this for symlinks:
{code}
lrwxrwxrwx   - cmccabe supergroup          0 2013-07-23 15:59 /alpha -> 
hdfs://localhost:6000/beta
{code}

* {{ClientNamenodeProtocolServerSideTranslatorPB}}: fix {{System.out.println}} 
that was left in the code.  It was preventing a unit test that looked at stdout 
from working.

* TestDFSShell: add unit tests for symlinks and ls of a symlink.
                
> FSShell should support creating symlinks
> ----------------------------------------
>
>                 Key: HDFS-4019
>                 URL: https://issues.apache.org/jira/browse/HDFS-4019
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: tools
>    Affects Versions: 2.0.3-alpha
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Minor
>         Attachments: HDFS-4019.001.patch
>
>
> FSShell should support creating symlinks.  This would allow users to create 
> symlinks from the shell without having to write a Java program.
> One thing that makes this complicated is that FSShell currently uses 
> FileSystem internally, and symlinks are currently only supported by the 
> FileContext API.  So either FSShell would have to be ported to FileContext, 
> or symlinks would have to be added to FileSystem.  Or perhaps we could open a 
> FileContext only when symlinks were necessary, but that seems messy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to