[
https://issues.apache.org/jira/browse/HDDS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521441#comment-16521441
]
Anu Engineer commented on HDDS-177:
-----------------------------------
[~elek] Thanks for the patch. Some very minor comments.
# SCMNodeManager:onMessage - Shouldn't we check if the command is null and also
verify that datanode ID is no-null or valid?
# StorageContainerManager.java -- unused import?
> Create a releasable ozonefs artifact
> -------------------------------------
>
> Key: HDDS-177
> URL: https://issues.apache.org/jira/browse/HDDS-177
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: Ozone Filesystem
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-177.001.patch, HDDS-177.002.patch,
> HDDS-177.003.patch, HDDS-177.004.patch, HDDS-177.005.patch,
> HDDS-177.006.patch, HDDS-177.007.patch
>
>
> The current ozonefs implementaton is under hadoop-tools/hadoop-ozone and uses
> the version of hadoop (3.2.0-SNAPSHOT currently) which is wrong.
> The other problem is that we have no single hadoop independent arfitact from
> ozonefs which could be used with any hadoop version.
> In this patch I propose the following modification:
> * move hadoop-tools/hadoop-ozone to hadoop-ozone/ozonefs and use the hdds
> version (0.2.1-SNAPSHOT)
> * Create a shaded artifact which includes all the required jar files to use
> ozonefs (hdds/ozone client)
> * Create an ozonefs acceptance test to test it with the latest stable hadoop
> version
--
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
