[
https://issues.apache.org/jira/browse/BEAM-11958?focusedWorklogId=564528&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-564528
]
ASF GitHub Bot logged work on BEAM-11958:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Mar/21 11:28
Start Date: 11/Mar/21 11:28
Worklog Time Spent: 10m
Work Description: iemejia commented on pull request #14199:
URL: https://github.com/apache/beam/pull/14199#issuecomment-796668962
Merged manually Thanks Alexey!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 564528)
Time Spent: 40m (was: 0.5h)
> 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)
