[jira] Commented: (LUCENE-703) Change QueryParser to use ConstantScoreRangeQuery in preference to RangeQuery by default

[ http://issues.apache.org/jira/browse/LUCENE-703?page=comments#action_12446837 ] Otis Gospodnetic commented on LUCENE-703: - I'm too tired to look at the patch, but I am +1 for this change in principal. Voted for it in JIRA, too. > Cha

[jira] Updated: (LUCENE-706) Index File Format - Example for frequency file .frq is wrong

[ http://issues.apache.org/jira/browse/LUCENE-706?page=all ] Doron Cohen updated LUCENE-706: --- Lucene Fields: [New, Patch Available] (was: [New]) > Index File Format - Example for frequency file .frq is wrong > -

[jira] Updated: (LUCENE-706) Index File Format - Example for frequency file .frq is wrong

[ http://issues.apache.org/jira/browse/LUCENE-706?page=all ] Doron Cohen updated LUCENE-706: --- Attachment: file-format-frq-example.patch example fixed > Index File Format - Example for frequency file .frq is wrong >

[jira] Created: (LUCENE-706) Index File Format - Example for frequency file .frq is wrong

Index File Format - Example for frequency file .frq is wrong Key: LUCENE-706 URL: http://issues.apache.org/jira/browse/LUCENE-706 Project: Lucene - Java Issue Type: Improvement

Re: ParallelMultiSearcher reimplementation

Hi Gus, : Is this development already taking place in the trunk? I was unable to : uncover any progress in this area. I haven't contributed to lucene (or : any open source project) before, but I would be willing to clean up a : number of things in this area if there was interest. I'm not aware o

Re: Lucene nightly build failure

So that's 2 days in a row that the nightly build has failed because of a connection timeout in TestRemoteSearchable .. the tests works locally (for me anyway) I don't know a lot about RMI, but the test seems to be doing the right thing: registering an RMI resource on localhost, and then connectin

Lucene nightly build failure

javacc-uptodate-check: javacc-notice: [echo] [echo] One or more of the JavaCC .jj files is newer than its corresponding [echo] .java file. Run the "javacc" target to regenerate the artifacts. [echo] init: common.compile-core: [mkdir] Created dir: /tm

ParallelMultiSearcher reimplementation

Hello everyone, We are currently using Lucene 1.9.1 at work. Using a profiler, I discovered that searching with a HitCollector in a ParallelMultiSearcher is single threaded. By extending ParallelMultiSearcher I was able to parallelize it without a problem (and without requiring a new lucene jar f

[jira] Commented: (LUCENE-704) Lucene should have a "write once" mode

[ http://issues.apache.org/jira/browse/LUCENE-704?page=comments#action_12446698 ] Yonik Seeley commented on LUCENE-704: - Found it: http://issues.apache.org/jira/browse/LUCENE-532 Looks like TermInfosWriter is the culprit. Personally, I think

[jira] Created: (LUCENE-705) CompoundFileWriter should pre-set its file length

CompoundFileWriter should pre-set its file length - Key: LUCENE-705 URL: http://issues.apache.org/jira/browse/LUCENE-705 Project: Lucene - Java Issue Type: Improvement Components: Ind

[jira] Resolved: (LUCENE-307) Lock obtain time out errors when opening readers and writers

[ http://issues.apache.org/jira/browse/LUCENE-307?page=all ] Michael McCandless resolved LUCENE-307. --- Resolution: Won't Fix Assignee: (was: Lucene Developers) > Lock obtain time out errors when opening readers and writers > --

[jira] Commented: (LUCENE-307) Lock obtain time out errors when opening readers and writers

[ http://issues.apache.org/jira/browse/LUCENE-307?page=comments#action_12446688 ] Michael McCandless commented on LUCENE-307: --- I think we can close this one? We now have locking implementation (*LockFactory) decoupled from directory i

[jira] Commented: (LUCENE-307) Lock obtain time out errors when opening readers and writers

[ http://issues.apache.org/jira/browse/LUCENE-307?page=comments#action_12446688 ] Michael McCandless commented on LUCENE-307: --- I think we can close this one? We now have locking implementation (*LockFactory) decoupled from directory i

[jira] Created: (LUCENE-704) Lucene should have a "write once" mode

Lucene should have a "write once" mode -- Key: LUCENE-704 URL: http://issues.apache.org/jira/browse/LUCENE-704 Project: Lucene - Java Issue Type: Improvement Components: Index Affects Version

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446678 ] Michael McCandless commented on LUCENE-701: --- > > In the future, it might be nice if there was an option to disable > > segments.gen to be more friendly to

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446677 ] Michael McCandless commented on LUCENE-701: --- Right, this is just normal contention. We do indeed retry around not only loading of segments_N but also th

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446665 ] Yonik Seeley commented on LUCENE-701: - > > In the future, it might be nice if there was an option to disable > > segments.gen to be more friendly to write-once

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446656 ] Ning Li commented on LUCENE-701: > That wouldn't be considered a failure because it's part of the retry logic. > At that point, an attempt would be made to open se

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446649 ] Yonik Seeley commented on LUCENE-701: - > 3 The reader tries to load seg_1 and fails. That wouldn't be considered a failure because it's part of the retry logi

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446638 ] Ning Li commented on LUCENE-701: Can the following scenario happen with lock-less commits? 1 A reader reads segments.1, which says the index contains seg_1. 2 A wr

[jira] Commented: (LUCENE-701) Lock-less commits

[ http://issues.apache.org/jira/browse/LUCENE-701?page=comments#action_12446628 ] Michael McCandless commented on LUCENE-701: --- Good questions! > In the future, it might be nice if there was an option to disable > segments.gen to be mor