[
https://issues.apache.org/jira/browse/HBASE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424189#comment-13424189
]
Zhihong Ted Yu commented on HBASE-6468:
---------------------------------------
{code}
+ if (!scanHasColumns) {
+ scan.setFilter(new FirstKeyOnlyFilter());
+ }
{code}
Can we enhance FirstKeyOnlyFilter so that the filter checks for designated
column before returning ReturnCode.NEXT_ROW ?
The rationale is that we want to speed up scan in case the designated column
appears in the first half of the row.
Please generate patch for trunk first.
No year is needed in license header.
Thanks
> RowCounter may return incorrect result if column name is specified in command
> line
> ----------------------------------------------------------------------------------
>
> Key: HBASE-6468
> URL: https://issues.apache.org/jira/browse/HBASE-6468
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.5
> Reporter: Shrijeet Paliwal
> Attachments:
> 0001-HBASE-6468-RowCounter-may-return-incorrect-result.patch
>
>
> The RowCounter use FirstKeyOnlyFilter regardless of whether or not the
> command line argument specified a column family (or family:qualifier).
> In case when no qualifier was specified as argument, the scan will
> give correct result. However in the other case the scan instance may
> have been set with columns other than the very first column in the
> row, causing scan to get nothing as the FirstKeyOnlyFilter removes
> everything else.
> https://issues.apache.org/jira/browse/HBASE-6042 is related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
