Simon0806 opened a new pull request #989: URL: https://github.com/apache/hadoop-ozone/pull/989
## What changes were proposed in this pull request?  Currently, when using o3fs, it will throw exception like above pic shows, it's because the dependency hadoop-ozone-filesystem-lib-legacy-$version.jar using maven dependency plugin to build, it picks all the dependencies , unpack then into a jar. However, this will make some configuration file be overlap because of the same file name, eg. ozone-default-generated.xml. When we use o3fs, it will read default configuration value of SCMClientConfig in ozone-default-generated.xml if we don't config in ozone-site.xml, however, ozone-default-generated.xml is not completed in legacy jar. So I use maven shaded plugin to replace maven dependency plugin, just like what hadoop-ozone-filesystem-lib-current does. The only difference is 'current' module will exclude some dependencies. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-3546 ## How was this patch tested? 1. Build the legacy jar. 2. Replace legacy jar in current cluster. 3. remove configuration "scm.container.client.idle.threshold" and "scm.container.client.max.size" 4. restart scm. 5. try o3fs, and it will not throw "client is null" exception ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
