[
https://issues.apache.org/jira/browse/HBASE-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348445#comment-16348445
]
Chia-Ping Tsai commented on HBASE-19824:
----------------------------------------
{quote}I got your mind...
if {{latestVersionOnly}} enable which means only check latest cell, and when
{{scan readAllVersions}}, then how to do with the following older version cells
which value is not match. If checks, it break the semantic meaning of
{{latestVersionOnly}}, otherwise, return numbers of mismatch value. Both are
weird...
{quote}
yep. If the function which only returns the matched cells is necessary, perhaps
we can introduce an new filter to address it.
> SingleColumnValueFilter returns wrong result when used in shell command
> -----------------------------------------------------------------------
>
> Key: HBASE-19824
> URL: https://issues.apache.org/jira/browse/HBASE-19824
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-4
> Reporter: Ted Yu
> Assignee: Reid Chan
> Priority: Major
> Attachments: HBASE-19824.master.001.patch,
> HBASE-19824.master.002.patch
>
>
> There are two cells in table t1:
> {code}
> ROW COLUMN+CELL
> r1 column=f1:a1,
> timestamp=1516313683984, value=a2
> r1 column=f1:b1,
> timestamp=1516313700744, value=b2
> {code}
> When SingleColumnValueFilter is used in shell command, no filtering was done:
> {code}
> hbase(main):022:0> scan 't1', {FILTER => "SingleColumnValueFilter('f1', 'a1',
> =, 'binary:a2')"}
> ROW COLUMN+CELL
> r1 column=f1:a1,
> timestamp=1516313683984, value=a2
> r1 column=f1:b1,
> timestamp=1516313700744, value=b2
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
