You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/10/04 23:29:20 UTC

[jira] [Resolved] (CALCITE-1110) remove or relocate shaded jackson in Avatica

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

Josh Elser resolved CALCITE-1110.
---------------------------------
    Resolution: Duplicate

Marking this as duplicate, but more correctly it is encapsulated by the changes in CALCITE-1224.

> remove or relocate shaded jackson in Avatica
> --------------------------------------------
>
>                 Key: CALCITE-1110
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1110
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>    Affects Versions: 1.6.0, 1.5.0
>            Reporter: Kai Gülzau
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: avatica-1.9.0
>
>
> The avatica jar includes a shaded version of jackson under the original package path.
> This shaded version interferes with other jackson versions in the classpath.
> Currently this prevents us from using jackson functionality which is only implemented in newer versions.
> https://mail-archives.apache.org/mod_mbox/calcite-dev/201602.mbox/%3C977C7450-18F4-48E2-A970-69B7E3E1BD2C%40apache.org%3E
> {quote}
> Is it reasonable to have a maven profile that uses jackson as “provided”[1] rather than shading? This would not be the default — the default would be continue to use a shaded version of jackson (relocated to org.apache.calcite.jackson, as Josh suggests) — but folks looking to embed calcite/avatica in a container might appreciate a lighter weight option.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)