hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11407) hbase-client should not require Jackson for pure HBase queries be executed
Date Tue, 24 Jun 2014 10:55:24 GMT

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

Sergey Beryozkin commented on HBASE-11407:

The patch is not about removing the dependency in hbase-client pom.xml, it simply moves Jackson
ObjectMapper static initialization into a dedicated utility: this will let those consumers
of HBase Client API who do not expect to do any sort of JSON formatting exclude Jackson dependency
in their own poms. In my case it is the Apache CXF server where not all users may want to
have Jackson dependencies.

Removing it completely as per the comment may be a better solution but I guess it is more
sensitive solution and may take longer to be done.

> 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
> Moving ObjectMapper to a dedicated utility will help. The patch will be attached.

This message was sent by Atlassian JIRA

View raw message