Uh oh!
There was an error while loading. Please reload this page.
HBASE-26762: Un-Deprecate and improve documentation for Scan#setRowPrefixFilter - #4119
Conversation
nielsbasjes
commented
Feb 19, 2022
I'm in doubt about the test that was added testRowPrefixFilterAndStartRow : This is effectively showing that if you use these functions incorrectly you get unexpected results. |
fe6c4b9 to
d35632fComparenielsbasjes
commented
Feb 20, 2022
As discussed with Duo Zhang I'm re-deprecating the old name and providing a replacement with a better (non-confusing) name: setStartStopRowForPrefixScan In addition to the Scan related method I found that both of these classes also have a method with the same name "setRowPrefixFilter" ./hbase-server/src/main/java/org/apache/hadoop/hbase/wal/WALPrettyPrinter.java ./hbase-mapreduce/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java |
Apache-HBase
commented
Feb 23, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 23, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 23, 2022
💔 -1 overall
This message was automatically generated. |
…efixFilter Signed-off-by: Niels Basjes <nielsbasjes@apache.org>
…d results Signed-off-by: Niels Basjes <nielsbasjes@apache.org>
…owForPrefixScan Signed-off-by: Niels Basjes <nielsbasjes@apache.org>
20500dd to
3129b5fCompareApache-HBase
commented
Feb 23, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 24, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 24, 2022
🎊 +1 overall
This message was automatically generated. |
Apache9
commented
Feb 26, 2022
Oh, one minor thing, I think we could also cherry-pick this change to branch-2 and branch-2.5, so let's change the javadoc from 'since 3.0.0' to 'since 2.5.0'? Thanks. |
Signed-off-by: Niels Basjes <nielsbasjes@apache.org>
nielsbasjes
commented
Feb 26, 2022
I've pushed it with since 2.5.0 now.
Just let me know if I have to do something from here. |
Apache9
commented
Feb 26, 2022
Our guideline is to remove a method which has been marked as deprecated for a whole major release, so usually, if a method is deprecated in 2.5.0, we will remove it in 4.0.0. Unless we found that this is a mistake, or the behavior is really confusing, we will remove it more aggressively. For this method, since it has been there for a long time, I tend to keep it there and only remove it in 4.0.0, so you could modify the javadoc to 'since 3.0.0, will be removed in 4.0.0'. And please fix the checkstyle issues? They are both line length issue, a simple format is enough to fix them. Thanks. |
Apache-HBase
commented
Feb 26, 2022
🎊 +1 overall
This message was automatically generated. |
Signed-off-by: Niels Basjes <nielsbasjes@apache.org>
nielsbasjes
commented
Feb 26, 2022
I think this should be 'since 2.5.0, will be removed in 4.0.0' ?
Done. |
Apache-HBase
commented
Feb 26, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 27, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 27, 2022
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 27, 2022
🎊 +1 overall
This message was automatically generated. |
Apache9
commented
Feb 27, 2022
|
Apache-HBase
commented
Feb 27, 2022
🎊 +1 overall
This message was automatically generated. |
nielsbasjes
commented
Feb 28, 2022
Is there anything I can do to fix this last error? |
…fixFilter (#4119) Signed-off-by: Andrew Purtell <apurtell@apache.org> Signed-off-by: Duo Zhang <zhangduo@apache.org>
…fixFilter (#4119) Signed-off-by: Andrew Purtell <apurtell@apache.org> Signed-off-by: Duo Zhang <zhangduo@apache.org>
Issue https://issues.apache.org/jira/browse/HBASE-26762
I found today that with ticket https://issues.apache.org/jira/browse/HBASE-25299 the intended effects of Scan#setRowPrefixFilter were unclear (hence the report of unexpected effects) and instead of just improving the documentation the method was marked as deprecated.
Quote:
Yes, if you use this very valuable method incorrectly it will yield incorrect results.
I strongly disagree with this deprecation because it is one of the most used methods of Scan in many of my applications.
I do agree the documentation should more clearly indicate these combinations do not work.
This pull request does only 2 things: