Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of bdelacretaz@gmail.com
 designates 209.85.221.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=YkhXnaSyNHSG50ff20BBLF+7VDOLPXLawemT9TnLcTH8FTaz8c1VGdhl+2cZZ2jSe9
         ZDy0TU1U5mF3jZ3oI6PuDJg8uRrTZyLm5AEw5skd1yJrq5EY9OOdA38KWxAmQS3KMK3P
         HaIVKfCQ9mWiStXmWbyQ+2V50fbmCsElmQkFE=
MIME-Version: 1.0
Sender: bdelacretaz@gmail.com
In-Reply-To: <697f8380906171433o22d8e8fbi3992b3fcac26f2ad@mail.gmail.com>
References: <9B333D29-9580-414C-B451-8CAB9EBA6ED1@tfd.co.uk>
	 <a781e7950906170113h364b05f2i486e72e92ad11263@mail.gmail.com>
	 <697f8380906170204t5e90030bp215fbadaeee1386d@mail.gmail.com>
	 <9BC2FD1A-9A05-4717-9F5B-E85A5B827027@tfd.co.uk>
	 <697f8380906171433o22d8e8fbi3992b3fcac26f2ad@mail.gmail.com>
Date: Thu, 18 Jun 2009 10:16:24 +0200
Message-ID: <f767f0600906180116u6159c562r28eb2381b6626e31@mail.gmail.com>
Subject: Re: Query that sorts a large result set.
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: users@jackrabbit.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

On Wed, Jun 17, 2009 at 11:33 PM, Ard Schrijvers
<a.schrijvers@onehippo.com> wrote:
> You though have to realize that, in my computions, I assume you are just
> using a Calendar value which is unique for each document. Now, if you would
> find it ok to stick to Calendar values with only, say, minute granularity,
> you'll significantly reduce (perhaps you won't have the issue anymore at
> all...if you would use a granalarity of hour (perhaps only in the prop you
> want for sorting, then 10 years will at most result in 87600 terms..not to
> much anymore)) the number of unique lucene terms for the calendar values,
> decreasing memory useage a lot....

Right, and maybe adding a second property P2, with a granularity of an
hour, allows one to solve this  without any changes to Jackrabbit: use
P2 to pre-select nodes where lastModified is in a give date range, and
then sort (at the application level) based on the actual lastModified
property.

Requires some simple application code, but I think that'd work fine.

-Bertrand