[jira] [Created] (HDDS-5035) Config not loaded when using an Ozone assembled jar

["Janus Chow (Jira)" <ji...@apache.org>]

Janus Chow created HDDS-5035:
--------------------------------

             Summary: Config not loaded when using an Ozone assembled jar
                 Key: HDDS-5035
                 URL: https://issues.apache.org/jira/browse/HDDS-5035
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Janus Chow


The issue happens when we were trying to do file operations in our own project with Hadoop-ozone-client assembled. Have attached the original config file.

The error is caused by the missing configs from hdds-common.  When we are building the fat-jar, there are different "ozone-default-generated.xml" files causing the conflict, and only one config file is kept. From the client-side, we can use the maven-shade-plugin to merge all "ozone-default-generated.xml" files as mentioned in HDDS-2250. But I think we'd better solve it from the server-side.

I have tried to add maven-shade-plugin in the module of hadoop-ozone-client and hadoop-ozone-common to only merge "ozone-default-generated.xml" files, but our own projects can not imply hadoop-hdds-common anymore.

I was thinking if we can change the logic of loading configs. For different modules to generate different config files, so that these files won't causing the conflict while still being able to load from different classpaths.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org