You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/04/20 08:28:00 UTC
[jira] [Updated] (HDDS-3458) Support Haddop 2.x with build-time
classpath separation intead of isolated classloader
[ https://issues.apache.org/jira/browse/HDDS-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Elek updated HDDS-3458:
------------------------------
Description:
Apache Hadoop Ozone is a Hadoop subproject. It depends on the released Hadoop 3.2. But as Hadoop 3.2 is very rare in production, older versions should be supported to make it possible to work together with Spark, Hive, HBase and older clusters.
Our current approach is using classloader based separation (ozonefs "legacy" jar), which has multiple problems:
1. It's quite complex and hard to debug
2. It couldn't work together with security
The issue proposes to use a different approach
1. Reduce the dependency on Hadoop (including the replacement of hadoop metrics and cleanup of the usage of configuration)
2. Create multiple version from ozonefs-client with different compile time dependency.
> Support Haddop 2.x with build-time classpath separation intead of isolated classloader
> --------------------------------------------------------------------------------------
>
> Key: HDDS-3458
> URL: https://issues.apache.org/jira/browse/HDDS-3458
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
>
> Apache Hadoop Ozone is a Hadoop subproject. It depends on the released Hadoop 3.2. But as Hadoop 3.2 is very rare in production, older versions should be supported to make it possible to work together with Spark, Hive, HBase and older clusters.
> Our current approach is using classloader based separation (ozonefs "legacy" jar), which has multiple problems:
> 1. It's quite complex and hard to debug
> 2. It couldn't work together with security
> The issue proposes to use a different approach
> 1. Reduce the dependency on Hadoop (including the replacement of hadoop metrics and cleanup of the usage of configuration)
> 2. Create multiple version from ozonefs-client with different compile time dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org