[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694917#action_12694917
]
Michael McCandless commented on LUCENE-1313:
--------------------------------------------
Jason, your last patch looks like it's taking the "flush first to RAM Dir"
approach I just described as the next step (on the java-dev thread), right?
Which is great!
So this has no external dependencies, right? And it simply layers on top of
LUCENE-1516.
I'd be very interested to compare (benchmark) this approach vs solely
LUCENE-1516.
Could we change this class so that instead of taking a Transaction object,
holding adds & deletes, it simply mirrors IndexWriter's API? Ie, I'd like to
decouple the performance optimization of "let's flush small segments ithrough a
RAMDir first" from the transactional semantics of "I process a transaction
atomically, and lock out other thread's transactions". Ie, the transactional
restriction could/should layer on top of this performance optimization for
near-realtime search?
> 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.patch, LUCENE-1313.patch, lucene-1313.patch,
> lucene-1313.patch, lucene-1313.patch, lucene-1313.patch
>
>
> Realtime search with transactional semantics.
> Possible future directions:
> * Optimistic concurrency
> * Replication
> Encoding each transaction into a set of bytes by writing to a RAMDirectory
> enables replication. It is difficult to replicate using other methods
> because while the document may easily be serialized, the analyzer cannot.
> I think this issue can hold realtime benchmarks which include indexing and
> searching concurrently.
--
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: [email protected]
For additional commands, e-mail: [email protected]
