hi all,
Does lucene support all fields with a term? Can I use "_all" intead
"fieldname"?
As Lucene's APIs example code:
...
// Parse a simple query that searches for "text":
QueryParser parser = new QueryParser(Version.LUCENE_CURRENT, "fieldname",
analyzer);
Query qu
Hi Mike and Uwe,
Thank you for your answers. It is clear, now.
Regards,
Aurélien
On 10.10.2014 12:32, Uwe Schindler wrote:
Hi,
every segment is executed on its own (every segment is its own index).
Every segment returns its own document ids and the result is the union
of them ranked by score
Hi,
every segment is executed on its own (every segment is its own index). Every
segment returns its own document ids and the result is the union of them ranked
by score using a PriorityQueue. There is no cross-segment term dictionary and
posting lists in Lucene. It was like that before Lucene
By intersection, do you mean a MUST clause on a BooleanQuery?
Lucene uses "doc at a time" scoring, so for BooleanQuery, all MUST'd
clauses are visiting the same doc (if they match) at a time, so we do
the intersection for that document all at once, within each segment,
across the N clauses.
Mike
Thanks Ahmet and Jose for you help :)
Regards,
Le 09/10/2014 18:29, Jose Fernandez a écrit :
When you return true from incrementToken() you tell Lucene to add your token to
the token stream. At the end of incrementToken() check for an empty token. If
it's empty then return incrementToken() to
Hi,
I know that Lucene uses a skip-list algorithm to search very fast even
if the query needs to calculate intersection between terms within a
segment. But what happened if it needs to calculate an intersection
between more than one segment? I suppose that skip-list cannot be used
anymore. Wh
