incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravikumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-290) NRT Updates using RAMDirectory & Swap
Date Fri, 25 Oct 2013 06:54:30 GMT

    [ https://issues.apache.org/jira/browse/BLUR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805097#comment-13805097
] 

Ravikumar commented on BLUR-290:
--------------------------------

It needs to take care of the following

1. A unified IndexWriter that adds incoming documents to RAM, but propagates dels to both
RAM & Disk.

2. A unified IndexReader that is able to co-ordinate between these 2 indexes, including NRT
re-open sequences. [Basically "ALL-or-NONE"]

3. A proper definition and behaviour of "commit", as it has no meaning in RAMDirectory. 

3. Unintentional but simultaneous merges happening in both RAM & Disk indexes.

4. A scalable RAMDirectory, that should not eat-up GC-cycles and perform at concurrent loads.
[Sample Patch was already attached, in Blur-220]

> NRT Updates using RAMDirectory & Swap
> -------------------------------------
>
>                 Key: BLUR-290
>                 URL: https://issues.apache.org/jira/browse/BLUR-290
>             Project: Apache Blur
>          Issue Type: New Feature
>    Affects Versions: experimental-dev
>            Reporter: Ravikumar
>
> 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
(v6.1#6144)

Mime
View raw message