You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/03/11 10:35:00 UTC

[jira] [Assigned] (BEAM-11958) Don't use new Jackson APIs to avoid classpath issues when parsing AWS configuration

     [ https://issues.apache.org/jira/browse/BEAM-11958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía reassigned BEAM-11958:
-----------------------------------

    Assignee: Ismaël Mejía

> 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
>
> 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. Reverting this change makes sense and we should only fix it when moving to Jackson 3.x



--
This message was sent by Atlassian Jira
(v8.3.4#803005)