On 3-Apr-08, at 4:24 PM, Jonathan Ariel wrote:
Is this depends on the number of documents that matches the query or
the
number of documents in the index?
This aspect is more depedent on the number of terms that the date
query translates into.
If in a 3 million documents index my query matches 4, having date
with a
precision of seconds could slow down the query?
Yes. Solr does range queries by taking the disjunction of a bunch of
term queries, so it is the total number of terms checked that is the
limiting factor.
It would be better to implement this using an ordered index that could
be binary-searched, but Solr isn't currently designed for that (though
I think range optimization algorithms would be a cool addition).
-Mike
On Thu, Apr 3, 2008 at 7:45 PM, Mike Klaas <[EMAIL PROTECTED]>
wrote:
On 3-Apr-08, at 2:14 PM, Jonathan Ariel wrote:
Hi,
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?
Range query is highly dependent on the total number of unique terms
covered by the range. If you are indexing dates with very high
precision
(e.g., milliseconds), this can consist of ridiculous numbers of
terms.
Try rounding the dates to something more granular when indexing.
-Mike
