hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1677) improve semantics of the hadoop dfs command
Date Mon, 06 Aug 2007 13:47:59 GMT

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

Enis Soztutar commented on HADOOP-1677:
---------------------------------------

+1 for unifying unix and hadoop fs semantics. I recall having some trouble about non-intuitive
behavior in FsShell.

> improve semantics of the hadoop dfs command
> -------------------------------------------
>
>                 Key: HADOOP-1677
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1677
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Nigel Daley
>            Priority: Minor
>
> HADOOP-230 cover syntax changes.  Capturing here some DFS command line semantic comments
between Doug and I:
> The goal for DFS should be "UNIX-like *when* possible".  The goals of HDFS are primarily
to be usable, scalable, reliable, high-performance, and, secondarily, not to be gratuitously
incompatible with UNIX.  So, when it's easy to be compatible, we certainly should.  But when
UNIX compatibility fights with one of those other goals, it may lose.
> Two examples of incompatibilities with UNIX (that will need to be evaluated against the
above goal), are:
> UNIX: cp foo bar succeeds if bar exists
> DFS: dfs -put foo bar fails if bar exists. (same for dfs -cp).
> UNIX: mkdir foo fails if foo exists
> DFS: dfs -mkdir succeeds silently if foo exists and is a directory (if foo is a file
than it fails).
> Many more such incompatibilities exist.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message