[
https://issues.apache.org/jira/browse/LUCENE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675523#action_12675523
]
jasonrutherglen edited comment on LUCENE-1516 at 2/20/09 5:42 PM:
-------------------------------------------------------------------
There's concurrency issues to work out.
- IW.getReader returns a cloned read only reader
- Removed IW.reopenReader
- All test methods pass except testAddIndexesAndDoDeletesThreads.
testAddIndexesAndDoDeletesThreads
currently merges indexes concurrently (and fails). In the future the
method will test merging, deleting, and searching concurrently.
- Concurrent merges fail when "ant test-core" is run
- DocumentsWriter.applyDeletes deletes again at the SegmentReader level
was (Author: jasonrutherglen):
There's concurrency issues to work out.
- IW.getReader returns a cloned read only reader
- Removed IW.reopenReader
- All test methods pass except testAddIndexesAndDoDeletesThreads.
testAddIndexesAndDoDeletesThreads
currently merges indexes concurrently (and fails). In the future the
method will test merging, deleting, and searching concurrently.
- Concurrent merges fail when "ant test-core" is run
- DocumentsWriter.applyDeletes deletes again at the SegmentReader level
- What happens when a user executes IR.clone(true) on a read only
reader?
> Integrate IndexReader with IndexWriter
> ---------------------------------------
>
> Key: LUCENE-1516
> URL: https://issues.apache.org/jira/browse/LUCENE-1516
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1516.patch, LUCENE-1516.patch, LUCENE-1516.patch,
> LUCENE-1516.patch, LUCENE-1516.patch, LUCENE-1516.patch, LUCENE-1516.patch,
> LUCENE-1516.patch
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> The current problem is an IndexReader and IndexWriter cannot be open
> at the same time and perform updates as they both require a write
> lock to the index. While methods such as IW.deleteDocuments enables
> deleting from IW, methods such as IR.deleteDocument(int doc) and
> norms updating are not available from IW. This limits the
> capabilities of performing updates to the index dynamically or in
> realtime without closing the IW and opening an IR, deleting or
> updating norms, flushing, then opening the IW again, a process which
> can be detrimental to realtime updates.
> This patch will expose an IndexWriter.getReader method that returns
> the currently flushed state of the index as a class that implements
> IndexReader. The new IR implementation will differ from existing IR
> implementations such as MultiSegmentReader in that flushing will
> synchronize updates with IW in part by sharing the write lock. All
> methods of IR will be usable including reopen and clone.
--
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]
