[
https://issues.apache.org/jira/browse/HADOOP-18619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687444#comment-17687444
]
Ayush Saxena commented on HADOOP-18619:
---------------------------------------
Trying to catch-up, The entire effort is to get rid of jsr311 as a direct
dependency(ok as shaded?) and have rs-api as a direct dependency to pave way
for Jackson upgrade, Did I catch the intent right?
Well playing with js311-Jersey-Jackson family isn't very safe(Downstream
projects like Tez pull these, and we have seen in past that creating issues),
and shading itself always look to me like a hack, I am not saying it would lead
to some problem or the other, but shading does have potential to cause issues.
To get rid of jsr311 and completely move to rs-api, we need to upgrade Jersey
as well(Akira did it for HDFS, not for other modules). So, the best way I feel
would be to explore upgrading jersey or may be to branched-Jersey or something
like that, as that I feel is the major blocking point for us to moving to
JDK-11 compile time support, Jersey as of today is blocking that as well...
> replace jsr311-api dependency with rs-api
> -----------------------------------------
>
> Key: HADOOP-18619
> URL: https://issues.apache.org/jira/browse/HADOOP-18619
> Project: Hadoop Common
> Issue Type: Task
> Components: build, common
> Reporter: PJ Fanning
> Priority: Major
>
> [jsr311-api|https://mvnrepository.com/artifact/javax.ws.rs/jsr311-api] is
> unmaintained and causes issues when jars bring in a dependency on the newer
> [rs-api|https://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api/2.1.1]
> jar - that uses the same package name but has incompatible code
> To make things worse, there is now a jakarta fork of rs-api but I suggest we
> worry about that later.
> jersey-core 1.19.x gives us the jsr311-api dependency.
> The upgrade to HADOOP-15984 is currently blocked and looks hard.
> HADOOP-15983 is a workaround that allows us to keep jersey 1.x but removes
> the issue where we end up relying on the unmaintained Jackson 1.9 jars.
> We may now need a similar fork of jersey-core 1.19 to build a version of that
> jar that uses rs-api instead of jsr311.
> The main benefit here is get around the fact that jackson jaxrs 2.13+ has
> dropped support for jsr311 and now only supports rs-api. (see HADOOP-18332)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
