[jira] Updated: (LUCENE-1313) Realtime Search

2009-06-04 Thread Jason Rutherglen (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Rutherglen updated LUCENE-1313: - Attachment: LUCENE-1313.patch * RAM buffer size is stored in the writer rather than set

Hudson build is back to normal: Lucene-trunk #849

2009-06-04 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/849/ - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org

Re: EnwikiDocMaker

2009-06-04 Thread Grant Ingersoll
On Jun 4, 2009, at 2:49 PM, Grant Ingersoll wrote: Looking more, I think my problem resides around the notion that I'm using EnWikiDocMaker independently of the benchmarking tool. The weird thing is, it used to work, but I don't know when it broke. I suspect I'm not initializing things r

Re: IR static methods

2009-06-04 Thread Earwin Burrfoot
Index/Commit/SegmentMetadata? Several classes, as you can reflect on various levels of the index. Some offtopic - SegmentInfo/SegmentsInfo should really be named Segment/Segments. That's exactly what these objects represent. You don't use names like PreparedStatementInfo or FileInfo or IntegerInfo

Re: IR static methods

2009-06-04 Thread Otis Gospodnetic
We have . $ ff \*Info\*java ./src/java/org/apache/lucene/index/FieldInfo.java ./src/java/org/apache/lucene/index/TermVectorOffsetInfo.java ./src/java/org/apache/lucene/index/SegmentInfo.java ./src/java/org/apache/lucene/index/TermInfosWriter.java ./src/java/org/apache/lucene/index/TermInfo.jav

[jira] Commented: (LUCENE-1677) Remove GCJ IndexReader specializations

2009-06-04 Thread Otis Gospodnetic (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716428#action_12716428 ] Otis Gospodnetic commented on LUCENE-1677: -- In my cca 10 year history of being ar

Re: EnwikiDocMaker

2009-06-04 Thread Grant Ingersoll
Looking more, I think my problem resides around the notion that I'm using EnWikiDocMaker independently of the benchmarking tool. The weird thing is, it used to work, but I don't know when it broke. I suspect I'm not initializing things right. Anyone else doing that? -Grant On Jun 3, 200

[jira] Commented: (LUCENE-1609) Eliminate synchronization contention on initial index reading in TermInfosReader ensureIndexIsRead

2009-06-04 Thread Yonik Seeley (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716376#action_12716376 ] Yonik Seeley commented on LUCENE-1609: -- It would be nice to fix, but I wonder how imp

[jira] Commented: (LUCENE-1567) New flexible query parser

2009-06-04 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716311#action_12716311 ] Grant Ingersoll commented on LUCENE-1567: - The software Grant has been received an

Re: ReadOnly IndexReaders

2009-06-04 Thread Shai Erera
So for this scenario I guess I would have like to know the reader is read-only. But if I understand you correctly, you say that writing my app such that one method get a reader for doing some job on non-deleted documents, while another get the same reader and might delete stuff is a bad design anyw

Re: ReadOnly IndexReaders

2009-06-04 Thread Yonik Seeley
On Thu, Jun 4, 2009 at 10:19 AM, Mark Miller wrote: > If you use hasDeletions() with a non read-only > Reader, then someone could delete out from under you, right? Right... but calling isDeleted() doesn't fix that (because of race conditions). You could call isDeleted(5) which would return false

[jira] Updated: (LUCENE-1488) issues with standardanalyzer on multilingual text

2009-06-04 Thread Robert Muir (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Muir updated LUCENE-1488: Attachment: LUCENE-1488.patch updated patch, not ready yet but you can see where i am going. ICUT

Re: ReadOnly IndexReaders

2009-06-04 Thread Mark Miller
Yonik Seeley wrote: On Thu, Jun 4, 2009 at 9:37 AM, Mark Miller wrote: I was thinking you have a read-only snapshot to check on the deletes though. Another thread can't do a delete with that Reader, and if they are doing it on another Reader, it wouldn't affect the snapshot the read-only Rea

Re: ReadOnly IndexReaders

2009-06-04 Thread Yonik Seeley
On Thu, Jun 4, 2009 at 9:37 AM, Mark Miller wrote: > I was thinking you have a read-only snapshot to check on the deletes though. > Another thread > can't do a delete with that Reader, and if they are doing it on another > Reader, it wouldn't > affect the snapshot the read-only Reader had opened?

Re: Build failed in Hudson: Lucene-trunk #848

2009-06-04 Thread Andi Vajda
On Jun 4, 2009, at 3:28, Michael McCandless wrote: Hmm -- problems downloading BDB's JARs from downloadds.osafoundation.org again... Yes, ISC, OSAF's ISP had a planned outage of 1.5 hr last night, CA time, to replace their core router rack. Andi.. Mike On Wed, Jun 3, 2009 at 10:1

Re: ReadOnly IndexReaders

2009-06-04 Thread Mark Miller
Yonik Seeley wrote: On Tue, Jun 2, 2009 at 4:54 AM, Shai Erera wrote: You could call reader.hasDeletions to decide whether you should call isdeleted()? But you cannot use that alone, since if a library receives an IndexReader, it cannot rely solely on hasDeletions, since at an upper level so

Re: ReadOnly IndexReaders

2009-06-04 Thread Yonik Seeley
On Tue, Jun 2, 2009 at 4:54 AM, Shai Erera wrote: > You could call reader.hasDeletions to decide whether you should call > isdeleted()? But you cannot use that alone, since if a library receives an > IndexReader, it cannot rely solely on hasDeletions, since at an upper level > someone might decide

[jira] Updated: (LUCENE-772) Index corruption can cause infinite spin loop when Lucene attempts to incorrectly uncompress fields

2009-06-04 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-772: -- Summary: Index corruption can cause infinite spin loop when Lucene attempts to incorrec

[jira] Reopened: (LUCENE-772) Lucene infinite loop? In FieldsReader.uncompress called from IndexSearcher.doc

2009-06-04 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reopened LUCENE-772: --- Reopening; nothing was fixed here... > Lucene infinite loop? In FieldsReader.uncompress

[jira] Commented: (LUCENE-772) Lucene infinite loop? In FieldsReader.uncompress called from IndexSearcher.doc

2009-06-04 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716234#action_12716234 ] Michael McCandless commented on LUCENE-772: --- Olivier, in your case are you certai

[jira] Assigned: (LUCENE-1609) Eliminate synchronization contention on initial index reading in TermInfosReader ensureIndexIsRead

2009-06-04 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-1609: -- Assignee: Michael McCandless > Eliminate synchronization contention on initial

[jira] Commented: (LUCENE-772) Lucene infinite loop? In FieldsReader.uncompress called from IndexSearcher.doc

2009-06-04 Thread Uwe Schindler (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716233#action_12716233 ] Uwe Schindler commented on LUCENE-772: -- Corrumptions are not automatically fixed, but

[jira] Commented: (LUCENE-1609) Eliminate synchronization contention on initial index reading in TermInfosReader ensureIndexIsRead

2009-06-04 Thread Michael McCandless (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716232#action_12716232 ] Michael McCandless commented on LUCENE-1609: I agree, we need to fix this for

[jira] Commented: (LUCENE-772) Lucene infinite loop? In FieldsReader.uncompress called from IndexSearcher.doc

2009-06-04 Thread Olivier Dony (JIRA)
[ https://issues.apache.org/jira/browse/LUCENE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716229#action_12716229 ] Olivier Dony commented on LUCENE-772: - I know this sounds silly on a 2y+ old issue, but

Re: Build failed in Hudson: Lucene-trunk #848

2009-06-04 Thread Michael McCandless
Hmm -- problems downloading BDB's JARs from downloadds.osafoundation.org again... Mike On Wed, Jun 3, 2009 at 10:10 PM, Apache Hudson Server wrote: > See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/848/changes > > Changes: > > [mikemccand] LUCENE-1660: make enablePositionIncrement req