hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-922) Bloom filters will not work if enabled after table is created and contains data
Date Wed, 22 Apr 2009 18:56:47 GMT

     [ https://issues.apache.org/jira/browse/HBASE-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-922.
-------------------------

    Resolution: Invalid

This issue became invalid when we moved to hfile.  We still need to deal with users enabling/disabling
bloom filters but the game has changed where this issue is concerned.

> Bloom filters will not work if enabled after table is created and contains data
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-922
>                 URL: https://issues.apache.org/jira/browse/HBASE-922
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.18.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> Currently it is possible to enable a bloom filter after a table is created and data has
been stored in it by disabling the table and modifying the column.
> While this correctly sets the attribute in the column descriptor, it does not create
bloom filters for existing data so that on the first compaction, an NPE will be thrown because
the HStore expects each HStoreFile to have a bloom filter.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message