You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Rong-En Fan (JIRA)" <ji...@apache.org> on 2009/03/31 12:09:52 UTC

[jira] Deleted: (HBASE-1300) HTable.getRow() returns null if the row does no exist

     [ https://issues.apache.org/jira/browse/HBASE-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rong-En Fan deleted HBASE-1300:
-------------------------------


> HTable.getRow() returns null if the row does no exist
> -----------------------------------------------------
>
>                 Key: HBASE-1300
>                 URL: https://issues.apache.org/jira/browse/HBASE-1300
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Rong-En Fan
>            Priority: Minor
>
> 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.