[
https://issues.apache.org/jira/browse/HBASE-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886463#action_12886463
]
Jonathan Gray commented on HBASE-2823:
--------------------------------------
This issue applies to DeleteFamily instances. (like ryan says, we have no
delete row)
The issue is that a DeleteFamily applies to all columns. In a row+col bloom,
you may not include a file which includes a DeleteFamily because that file
doesn't contain any instances of the column you are looking for. To ensure
that file would be included, we should include a key into the row+col bloom of
just the row, and when checking the blooms, we should check each for row+col
and for row. Note, this only applies to row+col, and in this case it is _only_
the DeleteFamilys that should add an additional key to the bloom.
> Entire Row Deletes not stored in Row+Col Bloom
> ----------------------------------------------
>
> Key: HBASE-2823
> URL: https://issues.apache.org/jira/browse/HBASE-2823
> Project: HBase
> Issue Type: Bug
> Components: filters, regionserver
> Affects Versions: 0.21.0
> Reporter: Nicolas Spiegelberg
> Fix For: 0.21.0
>
>
> If the user issues a Row Delete on an family with Row+Col blooms, that
> information is not currently detected by shouldSeek(). Possible known
> solutions are:
> 1. adding Row as Bloom Filter Key on Row Delete, shouldSeek() should do both
> a Row & Row+Col query for Row+Col filters.
> 2. keep delete information in a separate storage element.
> #1 seems like the best solution, but need to investigate further and fix this
> problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
