[
https://issues.apache.org/jira/browse/HBASE-14064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625836#comment-14625836
]
Hao Lin commented on HBASE-14064:
---------------------------------
Currently we modify the put call to pass "<cf>:" instead of "<cf>", which give
us the same semantic as before.
But it's difficult to find all the put calls with parameter "<cf>", they are
spread in different team and different projects.
What's more, we can not assure someone will not call with wrong argument again
in the future.
> 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)
