[
https://issues.apache.org/jira/browse/HBASE-20587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476150#comment-16476150
]
Josh Elser commented on HBASE-20587:
------------------------------------
{quote}You mean our JsonMapper has a reference to Jackson's ObjectMapper.
{quote}
Yes, thank you :)
{quote}should we shade jackson in hbase-thirdparty?
{quote}
Just had that same thought over on HBASE-20852. I'm not sure if there's a
reason we haven't yet shaded it, but that would help.
> Remove hbase-common Jackson dependency
> --------------------------------------
>
> Key: HBASE-20587
> URL: https://issues.apache.org/jira/browse/HBASE-20587
> Project: HBase
> Issue Type: Bug
> Components: dependencies
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Attachments: 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)
