incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <>
Subject [jira] [Commented] (BLUR-77) Fix the readonly version of BlurIndex
Date Sat, 27 Apr 2013 12:32:16 GMT


Aaron McCurry commented on BLUR-77:

1. We do not need the AbstractBlurIndex class anymore.  In a previous version the BlurWriterIndex
(before BlurNRTIndex) also extended the AbstractBlurIndex class.  So I think they can be simplified
into a single class if you think that will work better.
2. The read-only setting is possibly a a bad name, because what it means is that indexes will
not be opened with a writeable BlurIndex.  It doesn't mean that the indexes will never be
modified, we can't really prevent that.  So the refresher is there to check the index stored
in HDFS from time to time to see if it's been modified and reload the index.  A use case for
this would be indexes modified via a MapReduce job, where the reducer opens the index, writes
the changes and closes.  Then this class would check and reopen the index once changed.
3. Not much really, just test that it works.

Thanks, Gagan.
> Fix the readonly version of BlurIndex
> -------------------------------------
>                 Key: BLUR-77
>                 URL:
>             Project: Apache Blur
>          Issue Type: Bug
>    Affects Versions: 0.1.5
>            Reporter: Aaron McCurry
>             Fix For: 0.1.5
> If you try and create a readonly version of a Blur table it will fail because it's not

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message