Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Hadoop's Jersey dependencies are causing us real trouble.
I'm wondering if it would be a good idea to take the jersey and javax.ws code out of hadoop-common and move it into a dedicated hadoop-jersey1-common jar. We could later create a hadoop-jersey2-common.
hadoop-jersey1-common and hadoop-jersey2-common would have equivalent classes - just depend on different versions of Jersey.
Example code:
- https://github.com/apache/hadoop/blob/12498b35bbb754225b0b2ca90d5ad4f5cf628d56/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/http/HttpServer2.java#L1030
- https://github.com/apache/hadoop/blob/12498b35bbb754225b0b2ca90d5ad4f5cf628d56/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/HttpExceptionUtils.java#L89
Hadoop modules that need access to the common jersey code could start with depending on hadoop-jersey1-common but later be refactored to use hadoop-jersey2-common. We could do this on a module by module basis (one a time).
hadoop-common jar would have its jersey and jsr311-api dependencies removed.
Wdyt slfan1989, steve_l, ayushsaxena ?
Attachments
Issue Links
- is related to
-
HADOOP-19081 move ssh/sftp code out of hadoop-common into a dedicated jar
- Open
-
HADOOP-19077 Remove use of javax.ws.rs.core.HttpHeaders
- Resolved
- relates to
-
HADOOP-19075 add shaded jersey jar hadoop-shaded-jersey
- In Progress