You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2019/02/20 10:54:00 UTC

[jira] [Commented] (HBASE-20587) Replace Jackson with shaded thirdparty gson

    [ https://issues.apache.org/jira/browse/HBASE-20587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772897#comment-16772897 ] 

Duo Zhang commented on HBASE-20587:
-----------------------------------

Our rest framework also uses jackson and the replace work is not straight-forward so do not include it. Can do it in another issue I think.

> Replace Jackson with shaded thirdparty gson
> -------------------------------------------
>
>                 Key: HBASE-20587
>                 URL: https://issues.apache.org/jira/browse/HBASE-20587
>             Project: HBase
>          Issue Type: Bug
>          Components: dependencies
>            Reporter: Josh Elser
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0
>
>         Attachments: HBASE-20587-v1.patch, HBASE-20587.001.patch
>
>
> HBASE-20582 got me looking at how we use Jackson. It appears that we moved some JSON code from hbase-server into hbase-common via HBASE-19053. But, there seems to be no good reason why this code should live there and not in hbase-http instead. Keeping Jackson off the user's classpath is a nice goal.
> FYI [~appy], [~mdrob]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)