[
https://issues.apache.org/jira/browse/BLUR-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814523#comment-13814523
]
Aaron McCurry commented on BLUR-290:
------------------------------------
No problem on the code quality for now. I haven't had a chance to review the
code yet but just to be clear on the index states from your comments above.
State 1 - RAM Dir with NRT Writer (Used for reading and writing, rapid changes
in both directions)
State 2 - RAM Dir no longer being written to, but in the process of being
merged into the main writer (Read Only)
- This state has to occur because the ram index takes time to add and it
takes time for the main index to refresh the new data.
State 3 - Main index where the RAM Dirs are being added. (Read Only except for
bulk updates)
I will try to look through the code you have provided above in the next day or
two. Thanks for your help!
Aaron
> 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
> Attachments: BlurFlushingIndexWriter.java, BlurIndexTracker.java,
> BlurRealTimeIndex.java, BlurRealTimeIndexWriter.java,
> BlurRealTimeManager.java, BlurRealTimeManagerReopenThread.java,
> RealTimeTransactionRecorder.java, SlabAllocator.java, SlabRAMDirectory.java,
> SlabRAMFile.java, SlabRAMInputStream.java, SlabRAMOutputStream.java,
> SortingMultiReader.java
>
>
> 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)
