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-290) NRT Updates using RAMDirectory & Swap
Date Thu, 07 Nov 2013 23:41:18 GMT


Aaron McCurry commented on BLUR-290:

Actually having 2 index readers open at the same time is not as costly as you might think.
 Since the readers themselves are made up of immutable segments and really the only difference
between 2 versions of the same index is the different in segments and the delete masks.  Otherwise
they actually share the same resources.

Also Blur has a built in piece of code that closes readers once they are no longer in use.
 So when the BlurIndex hands our references to IndexReaders it increments their references.
 And when they are complete it closes them or releases the references.  Once those references
go to 0, the IndexCloser class will actually close the reader.

I'm not too worry about handing out a lot of reader references because what you have described
it what Blur does today.  It just uses the NRT code in Lucene.


> NRT Updates using RAMDirectory & Swap
> -------------------------------------
>                 Key: BLUR-290
>                 URL:
>             Project: Apache Blur
>          Issue Type: New Feature
>    Affects Versions: experimental-dev
>            Reporter: Ravikumar
>         Attachments:,,,,,,,,,,,,
> We have been discussing about handling humungous rows in Blur (BLUR-220). Explore the
idea of using RAMDirectory at the front, backed by persistent-index.

This message was sent by Atlassian JIRA

View raw message