incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravikumar (JIRA)" <>
Subject [jira] [Commented] (BLUR-290) NRT Updates using RAMDirectory & Swap
Date Tue, 03 Dec 2013 07:34:35 GMT


Ravikumar commented on BLUR-290:

I thinking through another idea.

Lucene has NRTCachingDirectory, which basically wraps a Disk-Directory as a delegate. All
incoming writes are written in RAM segments.

Reads just work normally. This is really useful for frequent NRT re-opens and will perform
very well under high write load, thereby automatically addressing Blur-295 issue also ["Long
pause during NRT re-opens]

We also don't need a big solution I previously proposed and instead all of it can be elegantly
handled with NRTCachingDirectory, in a single IndexWriter itself. 

Please let me know your views on this. If fine, I shall re-work the patch towards this approach.

> 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