Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Mon, 12 Mar 2007 13:45:45 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: java-user@lucene.apache.org
Subject: Re: date range querys
In-Reply-To: <359a92830703110920v5ebb4dfdvb3f40b9b76a01244@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0703121342380.10998@hal.rescomp.berkeley.edu>
References: <200703111702.27987.tkl@laposte.net>
 <359a92830703110920v5ebb4dfdvb3f40b9b76a01244@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: I suspect that if you stored your dates (use DateTools) as strings
: with a resolution of a day you'd get much faster queries, assuming
: that this is fine enough for your app.

...especialy if you use ConstanScoreRangeQUery ... if you find that isn't
fast enough, having the various granularities *may* help improve
performance, but only if they are stored in seperate fields (so the
when you query only at year granularity the termEnum doesn't have to
iterate over all the terms at finer granularity)

I've never tried this myself ... 99.99% of hte time i'm using Solr,
storing things with millisecond resolution, and trusting Solr's caching to
take care of makingthings fast enough for me (searching at day/hour
granularity 98% of the time makes that caching very effective)


-Hoss


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org