You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Cosmin Lehene (JIRA)" <ji...@apache.org> on 2015/01/08 08:45:34 UTC
[jira] [Resolved] (HBASE-6753) Potential bug in Put object
toString()
[ https://issues.apache.org/jira/browse/HBASE-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cosmin Lehene resolved HBASE-6753.
----------------------------------
Resolution: Cannot Reproduce
I'm suspecting a side effect of something else. Resolving as "cannot reproduce" [~wal] In case you think this is still happening please update accordingly.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)