incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravikumar (JIRA)" <>
Subject [jira] [Updated] (BLUR-290) NRT Updates using RAMDirectory & Swap
Date Tue, 19 Nov 2013 11:49:22 GMT


Ravikumar updated BLUR-290:


I was just trying a proof-of-concept stuff. There are many nocommits and loose ends, so haven't
really gone to the perf aspect. But if you can eval, will be great. I have fixed some bugs
and attached few test-cases, in case you want to try it.

+1 for introducing table-types. A less adventurous table-type can even write unsorted segments
to disk and take a hit during searches, while doing the balancing act during merge.

It would be great if we can detect that NRT re-opens are going to suffer under load and hence
adjust accordingly. Shouldn't it be a policy that is applicable to all table-types instead
of it being a table-type itself?

PS: Sorry for the huge number of files. Is there place to check-in, may be an experimental-branch?

> 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