[ http://issues.apache.org/jira/browse/LUCENE-665?page=all ]
Doron Cohen updated LUCENE-665:
---
Attachment: FSDirs_Retry_Logic_3.patch
I am attaching an updated patch - FSDirs_Retry_Logic_3.patch.
In this update:
- merge with code changes by issue 635
On Wednesday 30 August 2006 01:33, Doug Cutting wrote:
eks dev wrote:
Hi commiters, any chance of getting rid of BitSet in Filter? Can somebody
guide what else needs to be done to have it commited, we have a pair of hands
to help...
I'm looking at:
[
http://issues.apache.org/jira/browse/LUCENE-665?page=comments#action_12431533 ]
Michael McCandless commented on LUCENE-665:
---
But I am not sure how this should affect decision on applying this fix
- there would always be user
[
http://issues.apache.org/jira/browse/LUCENE-635?page=comments#action_12431540 ]
Michael McCandless commented on LUCENE-635:
---
With this change, Directory on DB, Directory on RAM, etc., still
work correctly. In fact you can completely
[
http://issues.apache.org/jira/browse/LUCENE-666?page=comments#action_12431541 ]
Grant Ingersoll commented on LUCENE-666:
I am not sure on this, so others should definitely contribute, but here's my
take:
The QueryParser (QP) is not
if MultiReader is constructed from array of subreaders (using publis
constructor) then calling isCurrent() method will throw
NullPointerException.
Testcase is attached below:
//-begin -TestMultiReaderIsCurrent.java --
package org.apache.lucene.index;
import java.io.IOException;
I'm happy to announce the first BETA of MUTIS (mutis.sourceforge.net). I
include a small demo on searching txt files (this kind of demo is like a
must ;) ).
I'm looking for more developers to archieve:
1- Plataform independence. Mutis run only under .NET, and I want it to run
under native
-- Forwarded message --
From: Mario Alejandro M. [EMAIL PROTECTED]
Date: 30-ago-2006 10:28
Subject: First BETA release of MUTIS
To: Lucene Developers List lucene-dev@jakarta.apache.org
I'm happy to announce the first BETA of MUTIS (mutis.sourceforge.net). I
include a small demo
[
http://issues.apache.org/jira/browse/LUCENE-664?page=comments#action_12431631 ]
Doug Cutting commented on LUCENE-664:
-
This is good stuff. Might it be better to include this in the javadoc? That
way, as the code evolves, the
[
http://issues.apache.org/jira/browse/LUCENE-72?page=comments#action_12431635 ]
Hoss Man commented on LUCENE-72:
I think the general issue here is that mixing syntax (ie: using AND, OR or NOT
along with + and -) is not something that works
[
http://issues.apache.org/jira/browse/LUCENE-72?page=comments#action_12431635 ]
Hoss Man commented on LUCENE-72:
I think the general issue here is that mixing syntax (ie: using AND, OR or NOT
along with + and -) is not something that works
[ http://issues.apache.org/jira/browse/LUCENE-25?page=all ]
Hoss Man updated LUCENE-25:
---
Summary: QueryParser produces empty BooleanQueries when all clauses are
stop words (was: [PATCH] StopFilter does not throw out parentheses)
Bugzilla Id: (was:
[
http://issues.apache.org/jira/browse/LUCENE-664?page=comments#action_12431645 ]
Grant Ingersoll commented on LUCENE-664:
Yeah, I thought about putting it in Javadoc and I share your concern about
invalidation, but I think that is
Paul,
my offer is valid, please shout if and where you need some help, test cases...
not t skilled with deep Lucene internals, but could help at least in API
view...
..
At the moment I don't remember what the FIXME's are about, so I'll
need a bit of time getting back into it.
Once
[ http://issues.apache.org/jira/browse/LUCENE-584?page=all ]
paul.elschot updated LUCENE-584:
Attachment: Matcher20060830.patch
As requested on java-dev, Matcher20060830.patch is the whole thing as a single
patch, relative to srv/java/org/apache/lucene
[
http://issues.apache.org/jira/browse/LUCENE-635?page=comments#action_12431666 ]
Doron Cohen commented on LUCENE-635:
We could (as you're suggesting) indeed extend FSDirectory so that it
provided the low level methods required by a
[
http://issues.apache.org/jira/browse/LUCENE-664?page=comments#action_12431669 ]
Steven Parkes commented on LUCENE-664:
--
I went through basically the same reasoning that Grant describes, particularly
with loading the javadocs w/too much
On Wednesday 30 August 2006 21:08, eks dev wrote:
Paul,
my offer is valid, please shout if and where you need some help, test
cases... not t skilled with deep Lucene internals, but could help at
least in API view...
Well, I just posted a single patch file, and I'd like to know whether
svn appy patch complains The file search/Searchable.java was found
twice!... I tried to appy patch from /src/java/org/apache/lucene on
current trunk...
- Original Message
From: Paul Elschot [EMAIL PROTECTED]
To: java-dev@lucene.apache.org
Sent: Wednesday, 30 August, 2006 9:49:41
On Wednesday 30 August 2006 22:40, eks dev wrote:
svn appy patch complains The file search/Searchable.java was found
twice!... I tried to appy patch from /src/java/org/apache/lucene on
current trunk...
That is because the file list I used contains search/Searchable.java twice.
It should
[
http://issues.apache.org/jira/browse/LUCENE-584?page=comments#action_12431684 ]
Yonik Seeley commented on LUCENE-584:
-
Thanks Paul,
I like the Matcher/Scorer relation.
It looks like no Filters currently return a matcher, so the current
[ http://issues.apache.org/jira/browse/LUCENE-584?page=all ]
paul.elschot updated LUCENE-584:
Attachment: Matcher20060830b.patch
Matcher20060830b.patch corrects 2 mistakes in Matcher20060830.patch:
Searchable.java was present twice, and
[
http://issues.apache.org/jira/browse/LUCENE-584?page=comments#action_12431696 ]
paul.elschot commented on LUCENE-584:
-
Yonik, as to you questions:
It looks like no Filters currently return a matcher, so the current patch
just lays the
Yonik,
issues.apache.org does not respond at the moment, so I'm answering here:
It looks like no Filters currently return a matcher, so the current patch
just lays the groundwork, right?
Right. Only the previous Filter-20060628.patch contains some commented FIXME
code to actually introduce a
[
http://issues.apache.org/jira/browse/LUCENE-584?page=comments#action_12431702 ]
Eks Dev commented on LUCENE-584:
using the latest Matcher20060830.patch
ant said BUILD SUCCESSFUL ;)
I will see how it works on some real life cases using our
On 8/30/06, Paul Elschot [EMAIL PROTECTED] wrote:
Well, I just posted a single patch file, and I'd like to know whether this
patch applies cleanly. The patch itself has 841 lines and affects 11 files,
so be careful, perhaps to the point of starting a new working copy.
FWIW, I usually check
[
http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12431757 ]
Jason Rutherglen commented on LUCENE-565:
-
I figured out the problem, the Solr DirectUpdateHandler2 expects to delete only
a certain number of documents
[
http://issues.apache.org/jira/browse/LUCENE-72?page=comments#action_12431760 ]
Dejan Nenov commented on LUCENE-72:
---
This makes sense. Iconcur that docs can be better - maybe we shoud lopen a
separate JIRA issue on that?
I propose this to
[
http://issues.apache.org/jira/browse/LUCENE-72?page=comments#action_12431760 ]
Dejan Nenov commented on LUCENE-72:
---
This makes sense. Iconcur that docs can be better - maybe we shoud lopen a
separate JIRA issue on that?
I propose this to
[
http://issues.apache.org/jira/browse/LUCENE-666?page=comments#action_12431761 ]
Dejan Nenov commented on LUCENE-666:
I propose that we throw a ParseException - it seems very straightforward to do
- any comments / concerns / objections?
[
http://issues.apache.org/jira/browse/LUCENE-305?page=comments#action_12431766 ]
Michael McCandless commented on LUCENE-305:
---
I think we can close this issue now that LUCENE-635 is resolved.
[PATCH] Lock Framework - allows custom
[
http://issues.apache.org/jira/browse/LUCENE-305?page=comments#action_12431766 ]
Michael McCandless commented on LUCENE-305:
---
I think we can close this issue now that LUCENE-635 is resolved.
[PATCH] Lock Framework - allows custom
[ http://issues.apache.org/jira/browse/LUCENE-305?page=all ]
Yonik Seeley closed LUCENE-305.
---
Fix Version/s: 2.0.1
Resolution: Duplicate
Assignee: Yonik Seeley (was: Lucene Developers)
[PATCH] Lock Framework - allows custom lock
[
http://issues.apache.org/jira/browse/LUCENE-666?page=comments#action_12431793 ]
Hoss Man commented on LUCENE-666:
-
A ParseException when
A OR NOT B is found might make sense, but what about A AND NOT B ... that
(to me anyway) means +A -B
34 matches
Mail list logo