[
https://issues.apache.org/jira/browse/HBASE-21922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771548#comment-16771548
]
Guanghao Zhang commented on HBASE-21922:
----------------------------------------
[INFO] Running org.apache.hadoop.hbase.regionserver.TestRowPrefixBloomFilter
[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.779 s
<<< FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRowPrefixBloomFilter
[ERROR]
testRowPrefixBloomFilter(org.apache.hadoop.hbase.regionserver.TestRowPrefixBloomFilter)
Time elapsed: 1.34 s <<< FAILURE!
java.lang.AssertionError: False negatives: 4 expected:<0> but was:<4>
at
org.apache.hadoop.hbase.regionserver.TestRowPrefixBloomFilter.testRowPrefixBloomFilter(TestRowPrefixBloomFilter.java:269)
The ut failed as index.rootBlockContainingKey(key, keyOffset, keyLength) may
return -1 when the key for bloom is small than the first index key...
FYI [~andrewcheng]
> BloomContext#sanityCheck may failed when use ROWPREFIX_DELIMITED bloom filter
> -----------------------------------------------------------------------------
>
> Key: HBASE-21922
> URL: https://issues.apache.org/jira/browse/HBASE-21922
> Project: HBase
> Issue Type: Bug
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Attachments: HBASE-21922.master.001.patch
>
>
> Assume we use '5' as the delimiter, there are rowkeys
> {code:java}
> 12345xxx
> 1235xxxx{code}
> When use ROWPREFIX_DELIMITED bloom filter, the rowkey write to bloom filter
> are
> {code:java}
> 1234
> 123{code}
> Then BloomContext#sanityCheck will failed.
> {code:java}
> private void sanityCheck(Cell cell) throws IOException {
> if (this.getLastCell() != null) {
> LOG.debug("Current cell " + cell + ", prevCell = " + this.getLastCell());
> if (comparator.compare(cell, this.getLastCell()) <= 0) {
> throw new IOException("Added a key not lexically larger than" + "
> previous. Current cell = "
> + cell + ", prevCell = " + this.getLastCell());
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
