[jira] [Commented] (HBASE-11407) hbase-client should not require Jackson for pure HBase queries be executed

["Nicolas Liochon (JIRA)" <ji...@apache.org>]

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

Nicolas Liochon commented on HBASE-11407:
-----------------------------------------

Who is calling this method? We can't just remove it from the client to simplify our dependencies?
If we don't remove it from the pom, or add a specific test, anyone can add the dependency back in any innocent patch (ok, transitive dependencies make this easy to break anyway, but still).

process-wise, we will need the patch for master as well (I've just checked, it contains this toJSON stuff as well...)

The master says 
{code}
  // TODO make this configurable
  // TODO Do we need this anymore now we have protobuffed it all?
{code}

I think we can just remove all this (from the client at least). [~saint.ack@gmail.com], wdyt?

> 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)