As a follow-on to this, the problem appears to have been PBKAC (problem
between keyboard and chair).
Sorting works fine as long as all indexes being referenced contain the field
being sorted. When executing a remote search, the container application
(that's me) needs to be sure to bubble up the ex
Hi
I am complete newbie to Lucene. In fact I'm not even a search guy. I looked
up terms such as stemming just yesterday. So this is going to be so much fun
;)
Here's the problem I am trying to solve:
I work in the B2B space at Staples (an office supplies company in the US).
We sell office products
Very interesting.
Actually, reading Meet Lucene Part 2 by Otis Gospondnetic and Eric Hatcher
there is mention of Egothor and MG4J. Egothor. What is not mentioned is
Carrot" which, I think, originally has been used with Egothor but has also
been submitted to Lucene CVS. There is a helpful discussion
On Oct 7, 2005, at 8:14 PM, Zhang, Lisheng wrote:
We recently encountered a strange behavior in
lucene v1.4.3 QueryParser: we call
QueryParser.parse("-1", "myidfield", new StandardAnalyzer());
and get retured query as:
-myidfield:1 // apparently we want "myidfield:-1"
Currently we can use
