[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714948#action_12714948
]
Michael McCandless commented on LUCENE-1313:
--------------------------------------------
{quote}
I want to run the Lucene unit tests in NRT mode without creating and/or
modifying all the test cases.
{quote}
You can just temporarily set the default then run all tests?
We never reached consensus on a back compat sort of setting...
{quote}
I ran a test case successfully that writes to a file while
opening threads that read from flushed sections on windows.
{quote}
Excellent; let's take this up under a new issue? If this holds true across
platform (and Windows is the most challenging one) then it'll make sharing much
easier.
{quote}
Closing docstores for every flush would seem to cause a lot of
overhead. With NRT + FSD aren't termvector files merged on disk for
every segment?
{quote}
Yes it adds overhead, though, it's not on the critical path for opening a new
reader since it happens in the BG. So... things like LUCENE-1526 (making
deletions, norms incrementally copy-on-write) I think are higher priority.
bq. Doesn't FSDir open only one FD per file?
No, it opens a real file every time openInput is called. I guess we could think
about having it share/clone internally?
> Realtime Search
> ---------------
>
> Key: LUCENE-1313
> URL: https://issues.apache.org/jira/browse/LUCENE-1313
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Affects Versions: 2.4.1
> Reporter: Jason Rutherglen
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1313.jar, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch, LUCENE-1313.patch,
> LUCENE-1313.patch, lucene-1313.patch, lucene-1313.patch, lucene-1313.patch,
> lucene-1313.patch
>
>
> Enable near realtime search in Lucene without external
> dependencies. When RAM NRT is enabled, the implementation adds a
> RAMDirectory to IndexWriter. Flushes go to the ramdir unless
> there is no available space. Merges are completed in the ram
> dir until there is no more available ram.
> IW.optimize and IW.commit flush the ramdir to the primary
> directory, all other operations try to keep segments in ram
> until there is no more space.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
