You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2024/08/27 16:06:00 UTC

[jira] [Resolved] (IMPALA-13082) Use separate versions for jackson-databind vs jackson-core, etc.

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

Joe McDonnell resolved IMPALA-13082.
------------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> Use separate versions for jackson-databind vs jackson-core, etc.
> ----------------------------------------------------------------
>
>                 Key: IMPALA-13082
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13082
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 4.5.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 4.5.0
>
>
> We have a single jackson-databind.version property defined populated by the IMPALA_JACKSON_DATABIND_VERSION. This currently sets the version for jackson-databind as well as other jackson libraries like jackson-core.
> Sometimes there is a jackson-databind patch release without a release of other jackson libraries. For example, there is a jackson-databind 2.12.7.1, but there is no jackson-core 2.12.7.1. There is only jackson-core 2.12.7. To handle these patch scenarios, it is useful to split out the jackson-databind version from the version for other jackson libraries.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org