You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2015/08/19 00:46:46 UTC

[jira] [Commented] (HBASE-14064) Thrift Server skip put operation without column qualifier but client is not aware of this.

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

Nick Dimiduk commented on HBASE-14064:
--------------------------------------

HBASE-9549 was a while back. Looks like I found no test coverage in the thrift module for this code path. Since puts don't make sense for the whole family, I think it's reasonable to throw an exception instead of just WARN.

> Thrift Server skip put operation without column qualifier but client is not aware of this.
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-14064
>                 URL: https://issues.apache.org/jira/browse/HBASE-14064
>             Project: HBase
>          Issue Type: Bug
>          Components: Thrift
>    Affects Versions: 0.98.0
>            Reporter: Hao Lin
>            Priority: Minor
>
> After upgrading from 0.94.6 to 0.98.6, we found that a Put return success at Thrift client side does not write the data actually. We found the following messages in HBase server log:
> 2015-07-13 16:41:13,513 WARN  [thrift-worker-0] thrift.ThriftServerRunner$HBaseHandler: No column qualifier specified. Delete is the only mutation supported over the whole column family.
> We found that the semantic of put operation with no column qualifier has changed.  It is treated as empty qualifier in 0.94, but it is skipped in 0.98. The client is not aware of this change at all, no return value, no exception. Maybe it's better to throw an exception than skip the operation silently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)