Hi all,
I am using Compass 1.1 with Lucene 2
Our product offers a 2 lucene sub-indexes per customer, A and B, where
B extends A.
In size, A & B are about 15G, where A =10G
We had a server failure a few days ago related to corrupt RAM, and
when the server came back up, and services restarted OK (
: If I am just searching for a term, "ipod" in this case, how would be coord
: computed? Would in this case coord(q,d) matter at all? (I understand that
: not)
in theory your SImilarity coord() function would be called to find out
what hte coord value for "1 of 1" should be ... but in reallity T
Hi,
I am adding Apache Lucene support for Querydsl
http://source.mysema.com/display/querydsl/Querydsl (which offers
type-safe queries for Java) and I am having problems understanding how
Lucene evaluates queries especially regarding negation in nested queries.
For instance the following two
Hi Steve,
I'm not sure what's wrong with the above (have you tried each of the two nested
SpanNot clauses independently?), but here's another thing to try:
Your query works. And as turns out, if I don't commit the same
embarrassing lower case / upper case inconsistency over and over aga