[jira] Resolved: (LUCENE-702) Disk full during addIndexes(Directory[]) can corrupt index

[ http://issues.apache.org/jira/browse/LUCENE-702?page=all ] Michael McCandless resolved LUCENE-702. --- Fix Version/s: 2.1 Resolution: Fixed Disk full during addIndexes(Directory[]) can corrupt index

Re: ThreadLocal leak (was Re: Leaking org.apache.lucene.index.* objects)

Otis, i figured out a similar problem when running a very heavy loaded search application in a servlet container. The reasone using ThreadLocals was to get rid of synchronized method calls e.g in TermVectorsReader which would break down the overall search performance. Currently i do not see

[jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459419 ] Michael McCandless commented on LUCENE-748: --- I think this (not releasing write lock on hitting an exception) is actually by design. It's because the

Stephen Hussey is out of the office.

I will be out of the office starting 12/18/2006 and will not return until 12/20/2006. I will respond to your message when I return.

[jira] Closed: (LUCENE-658) upload major releases to ibiblio

[ http://issues.apache.org/jira/browse/LUCENE-658?page=all ] Michael McCandless closed LUCENE-658. - Resolution: Duplicate Dup of LUCENE-551 upload major releases to ibiblio Key: LUCENE-658

[jira] Resolved: (LUCENE-734) Upload Lucene 2.0 artifacts in the Maven 1 repository

[ http://issues.apache.org/jira/browse/LUCENE-734?page=all ] Michael McCandless resolved LUCENE-734. --- Resolution: Fixed From the last comment, it looks like the 2.0 Lucene core JAR is in maven 1. Upload Lucene 2.0 artifacts in the Maven 1

Re: ThreadLocal leak (was Re: Leaking org.apache.lucene.index.* objects)

There is no inherent problem with ThreadLocal. It is a viable solution to synchronization issues in most cases. On Dec 18, 2006, at 11:25 AM, Bernhard Messer wrote: Otis, i figured out a similar problem when running a very heavy loaded search application in a servlet container. The

Re: potential indexing perormance improvement for compound index - cut IO - have more files though

A word of caution here... Using a shared FileChannel.pread actually performs a synchronization under Windows. See JDK bug http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6265734 I submitted this, and it was verified using the supplied test case. On Dec 17, 2006, at 1:31 PM, Doug

Re: potential indexing perormance improvement for compound index - cut IO - have more files though

robert engels wrote: Using a shared FileChannel.pread actually performs a synchronization under Windows. Sigh. Still, it'd be no worse than current FSDirectory on Windows. Doug - To unsubscribe, e-mail: [EMAIL PROTECTED]

Re: potential indexing perormance improvement for compound index - cut IO - have more files though

I think the important issues are index size, stability and number of concurrent readers. We achieved the best performance by using a pool of file descriptors to a segment so we could avoid the synchronization block, but this only worked for large, relatively unchanging segments. On Dec

[jira] Closed: (LUCENE-603) index optimize problem

[ http://issues.apache.org/jira/browse/LUCENE-603?page=all ] Michael McCandless closed LUCENE-603. - Resolution: Duplicate This looks like a dup of LUCENE-140 index optimize problem -- Key: LUCENE-603

[jira] Commented: (LUCENE-140) docs out of order

[ http://issues.apache.org/jira/browse/LUCENE-140?page=comments#action_12459457 ] Michael McCandless commented on LUCENE-140: --- I just resolved LUCENE-603 as a dup of this issue. It would be awesome if we could get a test case that

[jira] Commented: (LUCENE-140) docs out of order

[ http://issues.apache.org/jira/browse/LUCENE-140?page=comments#action_12459457 ] Michael McCandless commented on LUCENE-140: --- I just resolved LUCENE-603 as a dup of this issue. It would be awesome if we could get a test case that

[jira] Assigned: (LUCENE-129) Finalizers are non-canonical

[ http://issues.apache.org/jira/browse/LUCENE-129?page=all ] Michael McCandless reassigned LUCENE-129: - Assignee: Michael McCandless (was: Lucene Developers) Finalizers are non-canonical Key:

[jira] Assigned: (LUCENE-129) Finalizers are non-canonical

[ http://issues.apache.org/jira/browse/LUCENE-129?page=all ] Michael McCandless reassigned LUCENE-129: - Assignee: Michael McCandless (was: Lucene Developers) Finalizers are non-canonical Key:

[jira] Commented: (LUCENE-301) Index Writer constructor flags unclear - and annoying in certain cases

[ http://issues.apache.org/jira/browse/LUCENE-301?page=comments#action_12459479 ] Michael McCandless commented on LUCENE-301: --- I like Doug's solution add a new constructor, IndexWriter(Directory, Analyzer) which, if no such index

[jira] Commented: (LUCENE-301) Index Writer constructor flags unclear - and annoying in certain cases

[ http://issues.apache.org/jira/browse/LUCENE-301?page=comments#action_12459479 ] Michael McCandless commented on LUCENE-301: --- I like Doug's solution add a new constructor, IndexWriter(Directory, Analyzer) which, if no such index

[jira] Assigned: (LUCENE-301) Index Writer constructor flags unclear - and annoying in certain cases

[ http://issues.apache.org/jira/browse/LUCENE-301?page=all ] Michael McCandless reassigned LUCENE-301: - Assignee: Michael McCandless (was: Lucene Developers) Index Writer constructor flags unclear - and annoying in certain cases

[jira] Assigned: (LUCENE-301) Index Writer constructor flags unclear - and annoying in certain cases

[ http://issues.apache.org/jira/browse/LUCENE-301?page=all ] Michael McCandless reassigned LUCENE-301: - Assignee: Michael McCandless (was: Lucene Developers) Index Writer constructor flags unclear - and annoying in certain cases

[jira] Commented: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12459482 ] Paul Elschot commented on LUCENE-565: - I'd like to give this a try over the upcoming holidays. Would it be possible to post a single patch? A single patch can

[jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459483 ] Hoss Man commented on LUCENE-748: - given the changes made in LUCENE-702, i concur with your assesment Michael: keeping the lock open so that the caller can

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: IndexWriter.java) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: IndexWriter.July09.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: IndexWriter.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: NewIndexModifier.July09.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: NewIndexWriter.Aug23.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: NewIndexWriter.July18.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: TestWriterDelete.java) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: KeepDocCount0Segment.Sept15.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Updated: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=all ] Ning Li updated LUCENE-565: --- Attachment: (was: newMergePolicy.Sept08.patch) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459489 ] Jed Wesley-Smith commented on LUCENE-748: - I guess, particularly in light of LUCENE-702 that this behavior is OK - and the IndexReader.unlock(dir) is a

[jira] Commented: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12459490 ] Ning Li commented on LUCENE-565: Many versions of the patch were submitted as new code was committed to IndexWriter.java. For each version, all changes made were

[jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459491 ] Michael McCandless commented on LUCENE-748: --- OK I will update the javadoc for IndexWriter.close to make this clear. Thanks! Exception during

[jira] Assigned: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=all ] Michael McCandless reassigned LUCENE-748: - Assignee: Michael McCandless Exception during IndexWriter.close() prevents release of the write.lock

[jira] Commented: (LUCENE-748) Exception during IndexWriter.close() prevents release of the write.lock

[ http://issues.apache.org/jira/browse/LUCENE-748?page=comments#action_12459502 ] Jed Wesley-Smith commented on LUCENE-748: - Awesome, thanks! Exception during IndexWriter.close() prevents release of the write.lock

[jira] Commented: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12459506 ] Ning Li commented on LUCENE-565: Here is the design overview. Minor changes were made because of lock-less commits. In the current IndexWriter, newly added

access policy for Java Open Review Project

Hi all, I've been busy creating JOR accounts this weekend, and it was cool to see so many names from Lucene. Lucene, Solr, and Nutch have the lowest defect rates among the projects we've looked at, and I'm beginning to see why. One of the things JOR is doing is inviting people to come and help