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 21:10:25 GMT

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

Sergey Beryozkin commented on HBASE-11407:

The reason pom.xml is not updated is that the goal of the patch was to let consumers of hbase-client
who do pure HBase queries and wishing to optimize their dependencies exclude Jackson in their
own poms.
As far as I understand it may still be needed in certain cases. So I guess the dependency
needs to stay for now, with a provided patch most users will be able to exclude it if they
want to. I'm not sure making the dependency optional is the right solution given that it is
still used on some code paths (logging): one may say that a number of users who currently
depend on Jackson is at least no less than a number of users like me who want to exclude it
Thanks, Sergey 


> 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
>            Assignee: 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