Hey everyone,
I'm seeing some conflicting suggestions concerning the type of field to use
for indexing a Date/DateTime/Time value.
Some suggest conversion using DateTools.timeToString() and using a
StringField,
while others suggest using the long value of getTime() and using a
LongField (this is
Hi Frederik,
Both options would work but LongField (or LongPoint on Lucene 6.0+) would
indeed provide better performance for range queries. If you need to sort or
aggregate date values, you might also want to add a NumericDocValuesField.
Le mer. 5 avr. 2017 à 14:38, Frederik Van Hoyweghen <
frede
Let's say I want to search between 2 dates, search for a date that's
before/after another, etc (the usual stuff ^^ ), is this all with either
fieldtype?
Thanks for your reply!
Frederik
On Wed, Apr 5, 2017 at 3:04 PM, Adrien Grand wrote:
> Hi Frederik,
>
> Both options would work but LongField (
Hi,
a string field is the worst idea when you want to do range queries (from...to).
This will not scale and gets very slow on large indexes with many distinct
datetime values! In that case you should use a long field (LongField in Lucene
5, LongPoint in 6+) and search for a long range. For sort
