[ https://issues.apache.org/jira/browse/HBASE-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886459#action_12886459 ]
ryan rawson commented on HBASE-2823: ------------------------------------ Deleting an entire row is just entering a delete family in to every family, so it would make sense that these KeyValues would appear in both the row and row+col blooms if they exist. On Thu, Jul 8, 2010 at 1:26 PM, Nicolas Spiegelberg (JIRA) > 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.