. Is
MultiSearcher going to be deprecated and removed? Should one always use
MultiReader in order to get accurate results?
-Original Message-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Wednesday, November 10, 2010 1:19 PM
To: java-user@lucene.apache.org
Subject: Re: Search returnin
On Wed, Nov 10, 2010 at 1:04 PM, Uwe Schindler wrote:
> I know where the bug is...
>
> The problem has nothing to to with MultiSearcher at all, its just the
> rewritten query. Because (as Robert said) MultiSearcher rewrites per index,
> the rewritten query is different for each sub-index. The pr
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Wednesday, November 10, 2010 1:25 PM
> To: java-user@lucene.apache.org
> Cc: David Fertig
> Subject: Re: Sea
On Wed, Nov 10, 2010 at 8:05 AM, Erick Erickson wrote:
> Has anyone opened a JIRA on this?
>
I'm not sure if we should call it a bug or not (in this particular
example, it would be nice if we could find a fix i think though).
Because in general we can't guarantee MultiSearcher(Searcher...) will
Has anyone opened a JIRA on this?
Erick
On Wed, Nov 10, 2010 at 7:53 AM, Robert Muir wrote:
> On Sun, Nov 7, 2010 at 11:32 PM, Uwe Schindler wrote:
> > Does the same happen with a MultiReader on top of both indexes and using
> a
> > single IndexSearcher on top of this MultiReader?
> >
> > P.S.
On Mon, Nov 8, 2010 at 6:45 AM, Ian Lea wrote:
> This does seem extremely odd. David sent me a copy of his index and
> I've played around with it and also written a self-contained RAM index
> program, below, that shows the same problem, namely that if the second
> index has 1000+ docs the one and
On Sun, Nov 7, 2010 at 11:32 PM, Uwe Schindler wrote:
> Does the same happen with a MultiReader on top of both indexes and using a
> single IndexSearcher on top of this MultiReader?
>
> P.S.: How about using NumericField?
>
should be no problem there, it always uses filter rewrite?
the problem is
On Wed, Nov 10, 2010 at 7:00 AM, Robert Muir wrote:
> On Mon, Nov 8, 2010 at 6:45 AM, Ian Lea wrote:
>> This does seem extremely odd. David sent me a copy of his index and
>> I've played around with it and also written a self-contained RAM index
>> program, below, that shows the same problem, na
gt; Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
>> -Original Message-
>> From: David Fertig [mailto:dfer...@cymfony.com]
>> Sent: Monday, November 08, 2010 4:21 AM
>> To: java-user@luce
age-
> From: David Fertig [mailto:dfer...@cymfony.com]
> Sent: Monday, November 08, 2010 4:21 AM
> To: java-user@lucene.apache.org
> Subject: RE: Search returning documents matching a NOT range
>
> publish_date is a string, formatted as MMDD, so it string sorting
should
>
index
(as expected) and those terms are not in the second index.
David
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Sunday, November 7, 2010 11:12 AM
To: java-user@lucene.apache.org
Subject: Re: Search returning documents matching a NOT range
What kind o
n(e.getMessage());
>e.printStackTrace();
>}
>}
> }
>
> Output:
> MaxDocs for index 1: 1
> MaxDocs for index 2: 1000
> MaxDocs for MultiSearcher: 1001
> Query: +author:bentalcella -publish_date:[20100601 TO 20100630]
> Results: 1
> publish_date: 20100606
>
iSearcher: 1001
Query: +author:bentalcella -publish_date:[20100601 TO 20100630]
Results: 1
publish_date: 20100606
-Original Message-
From: Ian Lea [mailto:ian@gmail.com]
Sent: Friday, November 5, 2010 4:57 PM
To: java-user@lucene.apache.org
Subject: Re: Search returning documents matching a N
Do you get the bogus hit on the small index if search that index
alone? Are you positive it only holds the one doc? Loading the one
doc into a new RAM based index in the test would prove it.
You are more likely to get help if post a self-contained example -
people can see everything relevant and
14 matches
Mail list logo
