hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6753) Potential bug in Put object toString()
Date Mon, 10 Sep 2012 16:24:07 GMT

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

Ted Yu commented on HBASE-6753:
-------------------------------

In Operation.toString(), I see:
{code}
    try {
      return toJSON(maxCols);
    } catch (IOException ioe) {
      return toMap(maxCols).toString();
    }
{code}
Is jersey-json library on the classpath ?

If you can provide more log, that would help us analyze the problem.
                
> Potential bug in Put object toString()
> --------------------------------------
>
>                 Key: HBASE-6753
>                 URL: https://issues.apache.org/jira/browse/HBASE-6753
>             Project: HBase
>          Issue Type: Bug
>          Components: coprocessors
>         Environment: Cloudera CDH 4.0.1 with hbase 0.92.1-cdh4.0.1 
>            Reporter: Walter Tietze
>            Priority: Minor
>
> I'm a newbie to HBase.
> I implemented a coprocessor which is pretty nice with Cloudera version 4.0.1.
> Testing my copressor evolved a problem, because everytime I inserted logging into my
prePut-method, the Put object was not stored anymore into HBase.
> I analyzed the code and could reduce the problem to the fact, that calling the toString-method
on the Put object alone, is the reason for this behaviour.
> There seems to be a problem with the serialization of the object.
> Serialization seems to modifiy the object with the result, that it is not inserted in
HBase anymore.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message