[
https://issues.apache.org/jira/browse/HBASE-26762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niels Basjes updated HBASE-26762:
---------------------------------
Description:
Issue HBASE-25299 is about the Scan#setRowPrefixFilter having not the expected
effects when using also the setStartRow and/or setStopRow.
The setRowPrefixFilter is intended to make setting the right startRow and
stopRow for prefix scans. So it was always intended of using it instead of
doing separate setStartRow and/or setStopRow calls.
The reason for adding this to the Scan (~ 8 years ago) was that calculating the
correct start and stop row for doing the very efficient prefix scan is very
hard to do right.
This function is very important in many of my applications and with issue
HBASE-25299 it has now been marked as deprecated which I consider to be a very
bad idea.
I do agree the documentation can be improved on this point.
was:
Issue HBASE-25299 is about the Scan#setRowPrefixFilter having not the expected
effects when using also the setStartRow and/or setStopRow.
The setRowPrefixFilter is intended to make setting the right startRow and
stopRow for prefix scans. So it was always intended of using it instead of
doing separate setStartRow and/or setStopRow calls.
This function is very important in many applications we have and with issue
HBASE-25299 it has now been marked as deprecated which I consider to be a very
bad idea.
I do agree the documentation can be improved on this point.
> Scan#setRowPrefixFilter incorrectly marked as deprecated
> --------------------------------------------------------
>
> Key: HBASE-26762
> URL: https://issues.apache.org/jira/browse/HBASE-26762
> Project: HBase
> Issue Type: Bug
> Components: Client, scan
> Affects Versions: 3.0.0-alpha-2
> Reporter: Niels Basjes
> Priority: Major
>
> Issue HBASE-25299 is about the Scan#setRowPrefixFilter having not the
> expected effects when using also the setStartRow and/or setStopRow.
> The setRowPrefixFilter is intended to make setting the right startRow and
> stopRow for prefix scans. So it was always intended of using it instead of
> doing separate setStartRow and/or setStopRow calls.
> The reason for adding this to the Scan (~ 8 years ago) was that calculating
> the correct start and stop row for doing the very efficient prefix scan is
> very hard to do right.
> This function is very important in many of my applications and with issue
> HBASE-25299 it has now been marked as deprecated which I consider to be a
> very bad idea.
> I do agree the documentation can be improved on this point.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
