[
https://issues.apache.org/jira/browse/HDDS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648918#comment-16648918
]
Elek, Marton commented on HDDS-651:
-----------------------------------
Not clear where is the problem. Is it in the protocol part of the hadoop file
system? hdfs dfs -ls o3://.... As I remember we decided to use it as it's very
similar to s3. Most of the other connectors don't have fs postfix (except hdfs).
Personally I can't see any confusing part. This is o3, because this is o3
specific hadoop file system. What else could be? For me it's clean (and short).
Just fyi, o3 as protocol name is part of the branch-3.2 and will be released,
soon in case of rename branch-3.2 also should be modified.
> Rename o3 to o3fs for Filesystem
> --------------------------------
>
> Key: HDDS-651
> URL: https://issues.apache.org/jira/browse/HDDS-651
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Namit Maheshwari
> Priority: Blocker
> Fix For: 0.3.0
>
>
> I propose that we rename o3 to o3fs for Filesystem.
> It creates a lot of confusion while using the same name o3 for different
> purposes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
