[
https://issues.apache.org/jira/browse/HDDS-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928840#comment-16928840
]
Arpit Agarwal commented on HDDS-2121:
-------------------------------------
We have two ozone filesystem jars recently and neither works for us:
1. Current jar does not work as it includes unshaded Hadoop dependencies. These
can conflict with Hadoop dependencies already in the client's classpath.
2. Legacy jar does not work as it includes shaded Hadoop dependencies. This can
be problematic for versioning, e.g. a customer may upgrade their Hadoop version
and expect Ozone to use the new upgraded version without needing to upgrade
Ozone itself.
> Create a shaded ozone filesystem (client) jar
> ---------------------------------------------
>
> Key: HDDS-2121
> URL: https://issues.apache.org/jira/browse/HDDS-2121
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: build
> Reporter: Arpit Agarwal
> Priority: Blocker
>
> We need a shaded Ozonefs jar that does not include Hadoop ecosystem
> components (Hadoop, HDFS, Ratis, Zookeeper).
> A common expected use case for Ozone is Hadoop clients (3.2.0 and later)
> wanting to access Ozone via the Ozone Filesystem interface. For these
> clients, we want to add Ozone file system jar to the classpath, however we
> want to use Hadoop ecosystem dependencies that are `provided` and already
> expected to be in the client classpath.
> Note that this is different from the legacy jar which bundles a shaded Hadoop
> 3.2.0.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
