[ https://issues.apache.org/jira/browse/HBASE-20587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476110#comment-16476110 ]
Josh Elser commented on HBASE-20587: ------------------------------------ Looks like we can't rip out Jackson from the hbase-client as all operations (e.g. Get, Put) use it for implementing {{toString()}}. Can still pull it out of hbase-common and put that server-side in hbase-http. > 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 > > 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)