: quick. I'm using Lucene version 2.4.1
...
: and QueryParser. The search results between the two queries are now in
: different orders while the number of results are the same. I have one
: Old Way
: QueryParser parser = new QueryParser("words", analyzer);
: Query q = parser.parse("+wo
Yeah. I was thinking about of those. I don't want to upgrade as it is in
production. I can't get a test case that reproduces the issue for some reason.
I might need the production data set to test with.
I'll definitely try an explain and see what the heck is going on.
For now, I just reverted t
Odd. Query.toString() and back to Query via parser are not guaranteed
to be consistent but it looks pretty straightforward in this case.
Maybe Searcher.explain would give a clue. Or post a minimal
self-contained program or test case that demonstrates this. Or try a
later version of lucene.
--
I'm new to the list and I'm having an issue that I wanted to ask about quick.
I'm using Lucene version 2.4.1
I recently rewrote a query to use the Query classes rather than a String and
QueryParser. The search results between the two queries are now in different
orders while the number of resul
