On Thu, 3 Apr 2008 18:14:56 -0300
"Jonathan Ariel" <[EMAIL PROTECTED]> wrote:
> I'm experiencing a really poor performance when using date ranges in solr
> query. Is it a know issue? is there any special consideration when using
> date ranges? It seems weird because I always thought date dates are
> translated to strings, so internally lucene resolves everything the same
> way. So maybe the problem is with parsing the dates and traslating it to the
> internal value?
> Any suggestion?
Hi Jonathan,
I've seen this mentioned somewhere, but I cannot find the reference to it now.
from what I recall, it goes down to the DateField type having too much
precision (down to milliseconds, from memory). When you perform a range search,
it would check for each of those possibilities making it a huge and slow task.
The advice in that post / page was to use a string field which encoded the date
as YYYYMMDD...to as much precision as you want, and then handling the date
maths yourself on the app.
It may not work for you, and I could be completely wrong :)
b
_________________________
{Beto|Norberto|Numard} Meijome
"A Man that is good at excuses is usually good at nothing else"
Benjamin Franklin
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
