[ 
https://issues.apache.org/jira/browse/HBASE-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426113#comment-13426113
 ] 

Zhihong Ted Yu commented on HBASE-6468:
---------------------------------------

{code}
+   * Constructor which takes a list of columns. As soon as first KeyValue
{code}
Now that the parameter has changed to Set<byte []>, the above javadoc should be 
modified.
{code}
+   * matching any of these columns if found, filter moves to next row.
{code}
'if found' -> 'is found'.
{code}
+   * @param qualifiers the list of columns to me matched.
{code}
Change to 'the set of columns to be matched'

Looks like HBASE-6454 may go in ahead of this JIRA. So Filter.proto should have 
the following:
{code}
+message FirstKeyValueMatchingQualifiersFilter {
+}
{code}
                
> 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, 
> 0002-HBASE-6468-RowCounter-may-return-incorrect-result.patch, 
> 0004-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

        

Reply via email to