Wei-Chiu Chuang created HDDS-12763:
--------------------------------------
Summary: Update hadoop-dependency-client pom.xml exclude list
Key: HDDS-12763
URL: https://issues.apache.org/jira/browse/HDDS-12763
Project: Apache Ozone
Issue Type: Task
Affects Versions: 2.0.0
Reporter: Wei-Chiu Chuang
https://github.com/apache/ozone/blob/45eee3fa5d29f49eaed0758d1703d446d56e70fb/hadoop-hdds/hadoop-dependency-client/README.md#L15
{quote}
This helper project provides a reduced view to the Hadoop dependencies. Hadoop
common by default depends on a lot of other projects which are not required for
the parts used in Ozone.
The exclude rules should be updated on each version bump. If Hadoop introduce
new dependencies we need to exclude them (unless they are required).
{quote}
The last update to the hadoop-dependency-client pom.xml was 4 years ago and
when it was Hadoop 3.2.1. We are now at 3.4.1 and it needs to be tighten again.
I don't think it's a blocker for Ozone 2.0.0 though.
According to HDDS-3312, the process to make a reduced transitive dependencies:
{quote}
hadoop-ozone/common and hadoop-hdds/common projects are common between client
and server. Therefore we should remove any server side utilities / dependencies
from them as they would be added to the client classpath which makes harder the
Ozone client / ozonefs adoption.
hadoop-hdds should depend on a minimal set of hadoop dependencies (can be
managed a separated technical project / pom.xml)
code shared between server side projects (and not with the client) should be
moved to the framework
OM related code should be moved to the ozone-manager instead of ozone/common
{quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
