-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Lucene users,
On behalf of the Lucene dev community (a growing community far larger
than just the committers) I would like to announce the fourth release
candidate for Lucene 2.9.
Please download and check it out - take it for a spin and kick
Hi Uwe,
Thanks for the explanation! It really helps. That makes sense that for
a small number of values, such as hour NumericField is not going to
help me. I'm experimenting with using epoch NumericField for sorting,
which funnily is where I started with 2.4.1, before going down the
usual
NumericField uses a spezial encoding of terms for fast NumericRangeQueries.
It indexes more than one term per value. How many terms depends on the
precisionStep ctor parameter. If you set it to infinity (or something ge the
bit size of your value, 32 for ints, it indexes exactly one value).
Mark Miller wrote:
Hello Lucene users,
...
We let out a bug in the lock factory changes we made in RC3 -
making a new SimpleFSDirectory with a String param would throw
an illegal state exception - a fix for this is in RC4.
My apologies - not SimpleFSDirectory, but SimpleFSLockFactory.
Mark Miller wrote:
Hello Lucene users,
...
We let out a bug in the lock factory changes we made in RC3 -
making a new SimpleFSDirectory with a String param would throw
an illegal state exception - a fix for this is in RC4.
My apologies - not SimpleFSDirectory, but
Maybe I add this t the javadocs.
+1 - intuition might be to use it for anything numeric.
If we do not need a new RC fort hat I can do it tomorrow! I am not yet sure
what to write: I tend to say: Use NumericField, but with infinite
precisionStep for low-cardinality fields - and you get the
Uwe Schindler wrote:
Maybe I add this t the javadocs.
+1 - intuition might be to use it for anything numeric.
If we do not need a new RC fort hat I can do it tomorrow! I am not yet sure
what to write: I tend to say: Use NumericField, but with infinite
precisionStep for
If we do not need a new RC fort hat I can do it tomorrow! I am not yet
sure
what to write: I tend to say: Use NumericField, but with infinite
precisionStep for low-cardinality fields - and you get the old TermEnum
value list as before (with conversion through NumericUtils). In
general,
Hi Anshum,
Thanks for your insight. I will stick with the 20 fields.
I realized that I had neglected to mention that in a separate query I
will search on the primary key and a search term to return details about
how many hits come from each field. Is it safe to assume that this will
also not be
