Hi,
I'm trying to boost the score of documents containing some specific
terms using the setBoost()
method of the class SpanTermQuery (actually inherited from the class
Query) but this seems
to have no effect on the hits scores. Checking the way the scores are
computed (by calling the
explain
Hi all,
Is it possible, with the RAMDirectory (or another Directory), to flush
informations after each Document indexing ?
I tried this but this flush appears to be able to be made after 2 indexing at
best.
What do you think about it ? I forgot a configuration ?
Thanks,
Mickaël
Hi,
We have implemented a lucene search like this:
registry = LocateRegistry.getRegistry(RMIAddress, RMIPort);
searchables = new Searchable[] { (Searchable) registry.lookup(RMIIndexName)};
queryParser = new QueryParser(defaultField, new StandardAnalyzer());
Query query =
Hi,
i'm trying to collect Documents whose (normalized) score
is greater than a given threshold.
But i don't know what is the smartest way to do so :)
Do i have to subclass (Index)Searcher and override
search(Query query, Filter filter, final int nDocs)
to achieve this?
Kai Gülzau
Hi Mickaël,
Have you tried using minMergeDocs=1 ? Will that do what you want?
Otis
--- Rifflard Mickaël [EMAIL PROTECTED] wrote:
Hi all,
Is it possible, with the RAMDirectory (or another Directory), to
flush informations after each Document indexing ?
I tried this but this flush appears
Hi,
My guess is that the analyzer you use for indexing keeps the / (or
perhaps documenttype is a Keyword field, while the StandardAnalyzer and
QueryParser combination remove the / from the query string. Wildcards
work because they are not analyzed:
Hi Kai,
You could use HitCollector for this:
http://lucene.apache.org/java/docs/api/org/apache/lucene/search/HitCollector.html
Here are some bits about HitCollector:
http://www.lucenebook.com/search?query=hitcollector+score
A custom HitCollector comes with the book, and you can download the
Steven J. Owens wrote:
A friend just asked me for advice about synchronizing lucene
indexes across a very large number of servers. I haven't really
delved that deeply into this sort of stuff, but I've seen a variety of
comments here about similar topics. Are there are any well-known
Chris Lamprecht wrote:
I've done exactly what you describe, using N threads where N is the
number of processors on the machine, plus one more thread that writes
to the file system index (since that is I/O-bound anyway). Since most
of the CPU time is tokenizing/stemming/etc, the method works well.
Once an IndexReader is opened on an index, it's view of that index
never changes. Reuse the same IndexReader for all query requests and
ony reopen it after you do your optimize.
-Yonik
-
To unsubscribe, e-mail: [EMAIL
10 matches
Mail list logo