Hello,
I am running on Windows XP. Since our indices are constantly changing, we close
the searchers after each search.
I was running Lucene 1.4 and 1.4.1, and saw this problem. I replaced 1.4.1 with
1.4.2 on Friday, but haven't had a chance to observe its behavior since.
Would you say it's
Edwin Tang wrote:
Hello,
I am running on Windows XP. Since our indices are constantly changing, we close
the searchers after each search.
I was running Lucene 1.4 and 1.4.1, and saw this problem. I replaced 1.4.1 with
1.4.2 on Friday, but haven't had a chance to observe its behavior since.
Would
So i decicded to move my epoch date to the 20040608 date which fixed
my boolean query problem in regards to my current data size (approx
600,000)
but now as soon as I do a query like ... a*
I get the boolean error again. Google obviously can handle this query,
and I'm pretty sure
Hi,
For the following implementations:
1) storing boolean strings in fields X and Y separately
2) storing the same info in a field XY as 3 enums: X, Y, B, N meaning only X
is True, only Y is True, both are True or both are False
Is there significant performance gain when we substitute X:T OR
