[
https://issues.apache.org/jira/browse/HBASE-11407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041977#comment-14041977
]
Nicolas Liochon commented on HBASE-11407:
-----------------------------------------
bq. , it simply moves Jackson ObjectMapper static initialization into a
dedicated utility
Yeah, I saw that. That's what I'm saying it may break again at any time. In
this case I think that just removing the dependency is better as it lowers the
complexity instead of increasing it... It could be an issue for 0.98 (interface
change) but should be done for master as a part of this patch imho.
> 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)
