[
https://issues.apache.org/jira/browse/BEAM-11958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismaël Mejía updated BEAM-11958:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Triage Needed)
> Don't use new Jackson APIs to avoid classpath issues when parsing AWS
> configuration
> -----------------------------------------------------------------------------------
>
> Key: BEAM-11958
> URL: https://issues.apache.org/jira/browse/BEAM-11958
> Project: Beam
> Issue Type: Improvement
> Components: io-java-aws
> Reporter: Ismaël Mejía
> Assignee: Ismaël Mejía
> Priority: P2
> Fix For: 2.29.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We upgraded the Aws module to avoid deprecation Jackson messages in BEAM-8391
> however is pretty common that our users have older versions of Jackson in
> their clusters. If this happens their code will break because it won't find
> the new methods that Beam's Aws module is targeting.
> AWS SDKv1 for Java dependencies leak an older version of Jackson so this is
> pretty common for users on EMR who have the AWS dependencies pre provided in
> the cluster.
> Reverting this change makes sense and we should only upgrade these APIs when
> we decide to move to Jackson 3.x
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
