[
https://issues.apache.org/jira/browse/HBASE-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong-En Fan updated HBASE-1292:
-------------------------------
Assignee: Rong-En Fan
Affects Version/s: 0.19.0
Release Note: thrift's getRow*() now throws NotFound if the row key
does not exist
Hadoop Flags: [Incompatible change]
Status: Patch Available (was: Open)
With the patch, it correctly throws NotFound exception.
{code}
HP Fatal error: Uncaught exception 'NotFound' in
pear/thrift/packages/Hbase/Hbase.php:4064
Stack trace:
#0 pear/thrift/packages/Hbase/Hbase.php(706):
Hbase_getRow_result->read(Object(TBinaryProtocol))
#1 pear/thrift/packages/Hbase/Hbase.php(666): HbaseClient->recv_getRow()
#2 DemoClient.php(175): HbaseClient->getRow('demo_table', '00100-XXXX')
#3 {main} thrown in pear/thrift/packages/Hbase/Hbase.php on line 4064
{code}
> php thrift's getRow() would throw an exception if the row does not exist
> ------------------------------------------------------------------------
>
> Key: HBASE-1292
> URL: https://issues.apache.org/jira/browse/HBASE-1292
> Project: Hadoop HBase
> Issue Type: Bug
> Components: thrift
> Affects Versions: 0.19.1, 0.19.0
> Reporter: Rong-En Fan
> Assignee: Rong-En Fan
> Priority: Minor
> Attachments: 1292-0.19.patch, 1292.patch
>
>
> I've been played with thrift recently, and observed an unexpected behavior:
> when getRow() encounters an non-existent row key, it throws an exception like
> this:
> PHP Fatal error: Uncaught exception 'Exception' with message 'getRow failed:
> unknown result' in pear/thrift/packages/Hbase/Hbase.php:715
> Stack trace:
> #0 pear/thrift/packages/Hbase/Hbase.php(666): HbaseClient->recv_getRow()
> #1 htdocs/hbase/DemoClient.php(174): HbaseClient->getRow('demo_table',
> '00100-XXXX')
> #2 {main} thrown in pear/thrift/packages/Hbase/Hbase.php on line 715
> I would expect when we pass a non-existent key, it can throw something like
> NotFound (as in scanner) or one can test with RowResult.isEmpty() just like
> in java api.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
