Hi folks,
Here's a small tool that I'm releasing as open source. I hope some of
you might find it useful:
https://github.com/joelb-git/lqt
Lucene Query Tool (lqt) is a small utility for executing and
formatting Lucene queries from the command line (rather from inside a
graphical tool like Luke)
Hi folks,
I'm looking for some advice on the following scenario:
We have a large static index. Our application currently copies the
index wholesale and writes new docs to it, but the existing docs are
never deleted or changed. Our application is multithreaded, it uses
near-real-time search, and
> coord() and queryNorm() work on the query as a whole, which may span
> multiple fields.
Thanks for the response, but I'm still confused. In our use case, our
documents have two distinct types of fields, e.g.
Document:
A-field1
A-field2
A-field3
B-field1
B-field2
B-field3
In our ap
Hi folks,
I have a question on PerFieldSimilarityWrapper. It seems that it is
not possible to get per-field behavior on queryNorm() and coord()...
The documentation for PerFieldAnalyzerWrapper (lucene 4.0) says:
Subclasses should implement get(String) to return an appropriate
Similarity (fo
