[
https://issues.apache.org/jira/browse/HDDS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615216#comment-16615216
]
Bharat Viswanadham commented on HDDS-446:
-----------------------------------------
It's more or less just laziness. these two jars are copied to different
location and it was harder to handle version in the names. If you need it 1) we
can add the current version to the jar (eg. META-INF/...). It's more safe as it
can survive renames. 2) we can improve the build process to replace versions in
the docker files
I thought for this during copy we can use HDDS-VERSION as suffix, and in
docker-config we can add HDDS-VERSION. Let me know if i am missing something
here.
So, this is done for making hdfs datanode start ozone as a plugin (But we
cannot copy this jar in to any hdfs version, we can only copy to hdfs version
with which this jar is compiled. So, adding a hdfs version will it help here?),
and for scm and ksm we should use ozone distribution.
> Provide shaded artifact to start ozone service as a datanode plugin
> -------------------------------------------------------------------
>
> Key: HDDS-446
> URL: https://issues.apache.org/jira/browse/HDDS-446
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-446-ozone-0.2.001.patch
>
>
> Ozone datanode service could be started in two different way:
> # as a standalone process
> # as a datanode plugin
> We tested the second scenarion by compiling both ozone + hadoop trunk
> together and created a combined artifact. But we have no more full hadoop
> distribution in the ozone release package any more. And we had no answer how
> it could be started with an existing hadoop release.
> We need a well defined way to add the datanode-service to the classpath of
> the hadoop datanode.
> I propose here to create a lightweight shaded artifact (and here the shading
> only combines all the classes together without package name refactoring) to
> make it easier to extend an existing hadoop installation.
> In this patch I add the shade plugin execution to the ozone
> objectstore-service and the shaded file will be copied to the distribution.
> A new docker-compose based execution environment (ozone-hdfs)
> demonstrates/tests how it could work.
> Tested with hadoop 3.1.0 and datanode service could be started without any
> problem
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
