You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Shashikant Banerjee (JIRA)" <ji...@apache.org> on 2018/10/16 10:52:00 UTC
[jira] [Commented] (HADOOP-15857) Remove ozonefs class name
definition from core-default.xml
[ https://issues.apache.org/jira/browse/HADOOP-15857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651482#comment-16651482 ]
Shashikant Banerjee commented on HADOOP-15857:
----------------------------------------------
+1
> Remove ozonefs class name definition from core-default.xml
> ----------------------------------------------------------
>
> Key: HADOOP-15857
> URL: https://issues.apache.org/jira/browse/HADOOP-15857
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Blocker
> Attachments: HADOOP-15857-branch-3.2.001.patch
>
>
> Ozone file system is under renaming in HDDS-651 from o3:// to o3fs://. But branch-3.2 still contains a reference with o3://.
> The easiest way to fix it just remove the fs.o3.imp definition from core-default.xml from branch-3.2 as since HDDS-654 the file system could be registered with Service Provider Interface (META-INF/services...)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org