You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Teddy Choi (JIRA)" <ji...@apache.org> on 2013/10/11 03:32:43 UTC

[jira] [Updated] (HIVE-5277) HBase handler skips rows with null valued first cells when only row key is selected

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

Teddy Choi updated HIVE-5277:
-----------------------------

    Attachment: HIVE-5277.1.patch.txt

Modified HiveHBaseTableInputFormat#getRecordReader to follow http://hbase.apache.org/book/perf.reading.html 12.9.6. Optimal Loading of Row Keys. Added a related test file.

Now it returns correct results with this cases.

It also will make faster SELECT COUNT(rowky) FROM HBASE_TABLE than other COUNT usages. So it is considerable to use it for COUNT(1) cases, too.

> HBase handler skips rows with null valued first cells when only row key is selected
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-5277
>                 URL: https://issues.apache.org/jira/browse/HIVE-5277
>             Project: Hive
>          Issue Type: Bug
>          Components: HBase Handler
>    Affects Versions: 0.11.0, 0.11.1, 0.12.0, 0.13.0
>            Reporter: Teddy Choi
>            Assignee: Teddy Choi
>         Attachments: HIVE-5277.1.patch.txt
>
>
> HBaseStorageHandler skips rows with null valued first cells when only row key is selected.
> {noformat}
> SELECT key, col1, col2 FROM hbase_table;
> key1	cell1	cell2 
> key2	NULL	cell3
> SELECT COUNT(key) FROM hbase_table;
> 1
> {noformat}
> HiveHBaseTableInputFormat.getRecordReader makes first cell selected to avoid skipping rows. But when the first cell is null, HBase skips that row.
> http://hbase.apache.org/book/perf.reading.html 12.9.6. Optimal Loading of Row Keys describes how to deal with this problem.
> I tried to find an existing issue, but I couldn't. If you find a same issue, please make this issue duplicated.



--
This message was sent by Atlassian JIRA
(v6.1#6144)