lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1313) Realtime Search
Date Fri, 08 May 2009 09:07:45 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707283#action_12707283
] 

Michael McCandless commented on LUCENE-1313:
--------------------------------------------

{quote}
Does IW.optimize and IW.expungeDeletes operate on the ramdir as
well (the expungeDeletes javadoc implies calling
IR.numDeletedDocs will return zero when there are no deletes).
{quote}
I think IW.optimize should mean all RAM segments are merged into the single on-disk segment?

And IW.expungeDeletes should also apply to RAM segments, ie if RAM segments have pending deletes,
they are merged away (possibly entirely in RAM, ie the RAM merge policy could simply merge
to a new RAM segment)?

{quote}
In the patch the merge policies are split up which requires some
of the RAM NRT logic to be in updatePendingMerges.
One solution is to have a merge policy that manages merging to
ram and to disk,
{quote}

It looks like it's the "is it time to flush to disk" logic, right?  Why can't we make that
the purview of the RAM MergePolicy?  We may need to extend MergePolicy API to tell it how
much RAM is free in the budget.

bq. We should be able to rely on the directory in SegmentWriteState?

I think we should fix the indexing chain to always use SegmentWriteState's Directory and *not*
pass Directory to the ctors?  Does something go wrong if we take that approach?

> 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
>
>
> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message