[
https://issues.apache.org/jira/browse/LUCENE-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845745#action_12845745
]
Michael Busch edited comment on LUCENE-2312 at 3/16/10 6:51 AM:
----------------------------------------------------------------
The tricky part is to make sure that a reader always sees a consistent snapshot
of the index. At the same time a reader must not follow pointers to
non-published locations (e.g. array blocks).
I think I have a lock-free solution working, which only syncs (i.e. does
volatile writes) in certain intervals to not prevent JVM optimizations - but I
need more time for thinking about all the combinations and corner cases.
It's getting late now - need to sleep!
was (Author: michaelbusch):
The tricky part is to make sure that a reader always sees a consistent
snapshot of the index. At the same time a reader must not follow pointers to
non-published locations (e.g. array blocks).
I think I have a lock-free solution working, which only syncs in certain
intervals to not prevent JVM optimizations - but I need more time for thinking
about all the combinations and corner cases.
It's getting late now - need to sleep!
> Search on IndexWriter's RAM Buffer
> ----------------------------------
>
> Key: LUCENE-2312
> URL: https://issues.apache.org/jira/browse/LUCENE-2312
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Search
> Affects Versions: 3.0.1
> Reporter: Jason Rutherglen
> Assignee: Michael Busch
> Fix For: 3.1
>
>
> In order to offer user's near realtime search, without incurring
> an indexing performance penalty, we can implement search on
> IndexWriter's RAM buffer. This is the buffer that is filled in
> RAM as documents are indexed. Currently the RAM buffer is
> flushed to the underlying directory (usually disk) before being
> made searchable.
> Todays Lucene based NRT systems must incur the cost of merging
> segments, which can slow indexing.
> Michael Busch has good suggestions regarding how to handle deletes using max
> doc ids.
> https://issues.apache.org/jira/browse/LUCENE-2293?focusedCommentId=12841923&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12841923
> The area that isn't fully fleshed out is the terms dictionary,
> which needs to be sorted prior to queries executing. Currently
> IW implements a specialized hash table. Michael B has a
> suggestion here:
> https://issues.apache.org/jira/browse/LUCENE-2293?focusedCommentId=12841915&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12841915
--
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]
