Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of peterlkeegan@gmail.com
 designates 66.249.92.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=YkDSWzDqwQi7KPGzDWgpeZlt2xiQpBJoX1l+8q+M98p8XMBkDsLuEfybBBsHzKNxmUCWkuVqsK2KBC364jv9/41RGxtkmnRbUadMo23MWlFSwosOq+14H7Q9FMJc5w98OWCkJ39QEFMb71QZzwWVsOtHEk9qgPWZBMnjMpMhajc=
Message-ID: <e994873a0611031056wc507d8ds213d0c8115b576bd@mail.gmail.com>
Date: Fri, 3 Nov 2006 13:56:53 -0500
From: "Peter Keegan" <peterlkeegan@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: Announcement: Lucene powering Monster job search index (Beta)
In-Reply-To: <1c36b0de0611030801u320dff57k1a470eb93c239441@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_32533_968963.1162580213162"
References: <1c36b0de0611030801u320dff57k1a470eb93c239441@mail.gmail.com>

------=_Part_32533_968963.1162580213162
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Daniel,
Yes, this is correct if you happen to be doing a radius search and sorting
by mileage.
Peter

On 11/3/06, Daniel Rosher <rosherd@googlemail.com> wrote:
>
> Hi Peter,
>
> Does this mean you are calculating the euclidean distance twice ... once
> for
> the HitCollecter to filter
> 'out of range' documents, and then again for the custom Comparator to sort
> the returned documents?
> especially since the filtering is done outside Lucene?
>
> Regards,
> Dan
>
>
> >Joe,
> >
> >Fields with numeric values are stored in a separate file as binary values
> in
> >an internal format. Lucene is unaware of this file and unaware of the
> range
> >expression in the query. The range expression is parsed outside of Lucene
> >and used in a custom HitCollector to filter out documents that aren't in
> the
> >requested range(s). A goal was to do this without having to modify
> Lucene.
> >Our scheme is pretty efficient, but not very general purpose in its
> current
> >form, though.
> >
> >Peter
> >
> >
> >On 10/30/06, Joe Shaw <joeshaw@novell.com> wrote:
> >>
> >> Hi Peter,
> >>
> >> On Fri, 2006-10-27 at 15:29 -0400, Peter Keegan wrote:
> >> > Numeric range search is one of Lucene's weak points
> (performance-wise)
> >> so we
> >> > have implemented this with a custom HitCollector and an extension to
> the
> >> > Lucene index files that stores the numeric field values for all
> >> documents.
> >> >
> >> > It is important to point out that this has all been implemented with
> the
> >> > stock Lucene 2.0 library. No code changes were made to the Lucene
> core.
> >>
> >> Can you give some technical details on the extension to the Lucene
> index
> >> files?  How did you do it without making any changes to the Lucene
> core?
> >>
> >> Thanks,
> >> Joe
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-user-help@lucene.apache.org
> >>
> >>
>
>

------=_Part_32533_968963.1162580213162--