On Friday 12 May 2006 00:12, Chris Hostetter wrote:
>
> : >Boolean match = null;
> :
> : As for the thoughts question below: this java-dev, not c-dev :)
>
...
>
> ...i'm not trying to use null for false, i'm using null to indicate that
> wether or not a match occured has not been explicitly
-- Forwarded message --
From: wu fox <[EMAIL PROTECTED]>
Date: 2006-5-21 下午8:58
Subject: How to combine results from several indices
To: [EMAIL PROTECTED]
Hi all:
I have several indices and each index describe part of a document.
For example ,a index contains dublin core informa
wu fox wrote on 05/21/2006 03:02 AM:
> I have several indices and each index describe part of a document.
> For example ,a index contains dublin core information of a document,
> and another index contains some classification information of the same
> document. If I have a query "title:lucene AND
"Any thoughts on whether such a Matcher would be preferable to
a DocNrSkipper that only has this method:
int nextDocNr(int docNr)
?"
As far as I can comprehend, it makes a lot of sense to decouple Scoring from
Matching (of course their intermixing as well). This would practically mean
that
On Sunday 21 May 2006 21:06, eks dev wrote:
>
> "Any thoughts on whether such a Matcher would be preferable to
> a DocNrSkipper that only has this method:
> int nextDocNr(int docNr)
> ?"
>
> As far as I can comprehend, it makes a lot of sense to decouple Scoring from
Matching (of course their
[ http://issues.apache.org/jira/browse/LUCENE-544?page=all ]
Karl Wettin updated LUCENE-544:
---
Attachment: MultiFieldQueryParser.java.diff
I must have uploaded a bad version last time. Sorry. There was a compilation
problem in:
public static Query parse(
Thank you chuck !!! That really helps me.By the way ,Is there a good
algorithm to meet the constraints of ParallelReader,or some others
have implemented some code for it? Thank you
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Some of the indices are time-sensitive,so a transaction may not suit
for me. Can some method meet the time requirement besides the
constraints of parallelReader?Thank you again
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Wu,
I don't know of a general solution that you could get now.
I do have such a solution, but it is part of a much larger mechanism.
My Company will likely authorize contribution of this code if there is
sufficient community interest in using and enhancing it. I plan to
describe the capabilitie
I think it would be hard as there are many places in Lucene where it is
assumed that doc-ids uniquely identify a document. This is the main
reason that ParallelReader has these constraints.
Are you sure the transactionalizing updates to sub-indexes will cause
you performance problems? My applica
I greatly appreciate your help Chuck .Thanks again ：)
11 matches
Mail list logo
