You could use ValueSourceQuery for this - see
o.a.l.search.function. The trick is to create
your ValueSource class that is using two
FieldCacheSource objects - one for each location.
See http://issues.apache.org/jira/browse/LUCENE-1019
for a related example.
Note however that this solution would
hello--
i'm using MoreLikeThis. i'm trying to run the document comparison across more
than one field in my index, but i'm not at all sure that it's actually
happening -- when i examine the constructed query, only one field is mentioned!
here's my code:
FileReader reader = new
Hi Guys,
There is something in the Lucene that disturbs me. My question is about
sorting. In the queries there are used collator objects that sort the
results (in the class FieldSortedHitQueue). But in the indexing process
they are not used. As I now all the terms are ordered during the
Hi Guys,
We have implemented per field setting of Analyzers, based on the
language that is used for the responding field. Example: field FileName
is in English, field Content in Chinese. This we do by creating our
class that implements Analyzer and wraps two analyzers StandardAnalyzer
and
On Sunday 21 October 2007 17:21, Chris Sizemore wrote:
i'm using MoreLikeThis. i'm trying to run the document comparison across
more than one field in my index, but i'm not at all sure that it's
actually happening -- when i examine the constructed query, only one
field is mentioned! here's my
On Sunday 21 October 2007 17:21, Chris Sizemore wrote:
i'm using MoreLikeThis. i'm trying to run the document comparison across
more than one field in my index, but i'm not at all sure that it's
actually happening -- when i examine the constructed query, only one
field is mentioned! here's my
There's also an example of something very similar in Lucene In Action.
Erick
On 10/20/07, Johnny R. Ruiz III [EMAIL PROTECTED] wrote:
Hi All,
I was looking for a way to do a range query on 2 numeric field of my
index. The tricky part is, I don't directly use the numeric field but I
have
: 1. Are Range queries work correctly with all languages for which
: there are analyzers? (for example CJK and Thai);
Terms when indexed are allways ordered lexigraphically (using
Term.compareTo which uses String.compareTo) ... regardless of what field
or language they are in, so Range
