[
https://issues.apache.org/jira/browse/HADOOP-18033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565145#comment-17565145
]
Viraj Jasani edited comment on HADOOP-18033 at 7/11/22 7:04 PM:
----------------------------------------------------------------
{quote}Currently I recommend downgrading to 2.12.7 in both trunk and
branch-3.3. That way we don't need to treat HADOOP-15984 as a blocker for 3.4.0.
{quote}
I understand that if we are doing the revert with a new Jira, the new Jira
should ideally land on trunk before making it's way to active release branches,
but Jackson downgrade to 2.12.7 and removal of javax.ws.rs-api would also
likely need to be reverted as part of HADOOP-15984, so for HADOOP-15984 it will
be too much work staying upto date with trunk (it's already struggling to do so
btw with whatever progress is made), and now it will have to reintroduce
javax.ws.rs-api and remove jsr311-api. So far I have jsr311-api removed from
the current local patch, but if trunk removes javax.ws.rs-api as part of revert
of HADOOP-18033 on trunk, there will be rework (basically, revert of revert of
HADOOP-18033 for HADOOP-15984 to make progress) that would make the overall
progress for HADOOP-15984 even more complicated.
Hence, I am requesting if we could only restrict the revert of HADOOP-18033 for
branch-3.3 to unblock 3.3.4 release. Overall, it would be as if this Jira's fix
version was only meant for 3.4.0.
was (Author: vjasani):
{quote}Currently I recommend downgrading to 2.12.7 in both trunk and
branch-3.3. That way we don't need to treat HADOOP-15984 as a blocker for 3.4.0.
{quote}
I understand that if we are doing the revert with a new Jira, the new Jira
should ideally land on trunk before making it's way to active release branches,
but Jackson downgrade to 2.12.7 and removal of javax.ws.rs-api would also
likely need to be reverted as part of HADOOP-15984, so for HADOOP-15984 it will
be too much work staying upto date with trunk (it's already struggling to do so
btw with whatever progress is made), and now it will have to reintroduce
javax.ws.rs-api and remove jsr311-api. So far I have jsr311-api removed from
the current local patch, but if trunk removes javax.ws.rs-api as part of revert
of HADOOP-18033 on trunk, there will be rework (basically, revert of revert of
HADOOP-18033 for HADOOP-15984 to make progress) that would make the overall
progress for HADOOP-15984 even more complicated.
Hence, I am requesting if we could only restrict the revert of HADOOP-18033 for
branch-3.3 to unblock 3.3.4 release.
> Upgrade fasterxml Jackson to 2.13.0
> -----------------------------------
>
> Key: HADOOP-18033
> URL: https://issues.apache.org/jira/browse/HADOOP-18033
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Akira Ajisaka
> Assignee: Viraj Jasani
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.2
>
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> Spark 3.2.0 depends on Jackson 2.12.3. Let's upgrade to 2.12.5 (2.12.x latest
> as of now) or upper.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
