[
https://issues.apache.org/jira/browse/HBASE-11407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042001#comment-14042001
]
Sergey Beryozkin commented on HBASE-11407:
------------------------------------------
IMHO you are over complicating it. This is not a bug fix, when you say it will
'break again' it is just confusing. Your claim it is about increasing the
complexity is also not accurate. The patch moves the ObjectMapper only on the
path where it might be needed, i.e, on to toJson(...) code path. Right now it
is needed no matter what, whether toJson will be called or not.
> hbase-client should not require Jackson for pure HBase queries be executed
> ---------------------------------------------------------------------------
>
> Key: HBASE-11407
> URL: https://issues.apache.org/jira/browse/HBASE-11407
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Affects Versions: 0.98.3
> Reporter: Sergey Beryozkin
> Priority: Minor
> Fix For: 0.98.4
>
> Attachments: diff.txt
>
>
> Including the hbase-client module dependency and excluding Jackson
> dependencies causes the pure HBase query (run with HTableInterface) fail with
> Jackson ObjectMapper ClassNotFoundException.
> This is due to org.apache.hadoop.hbase.client.Operation having ObjectMapper
> statically initialized.
> Moving ObjectMapper to a dedicated utility will help. The patch will be
> attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
