Hi John,
On Wednesday 17 August 2005 04:46, John Wang wrote:
> Hi:
>
>I posted a bug (36147) a few days ago and didn't hear anything, so
> I thought I'd try my luck on this list.
>
>The idea is to avoid score calculations on documents to be filtered
> out anyway. (e.g. via Filter object
Hi:
I posted a bug (36147) a few days ago and didn't hear anything, so
I thought I'd try my luck on this list.
The idea is to avoid score calculations on documents to be filtered
out anyway. (e.g. via Filter object passed to the searcher class)
This seems to be an easy change.
Also
Under many usecases a date field is often indexed. If the granularity
of the date value is in milliseconds, the number of unique terms in
the index could potentially be huge.
So if this is indeed the case, it is a potential scalability
bottleneck in lucene index size.
Thanks
-John
On 8/12/05, C
Thanks Ben!
-Original Message-
From: Ben Litchfield <[EMAIL PROTECTED]>
Sent: Aug 15, 2005 6:33 PM
To: java-user@lucene.apache.org, Andrew Boyd <[EMAIL PROTECTED]>
Subject: Re: Integrating lucene search with adobe search
Andrew,
There are a couple different open parameters that can be p
thanks for looking into it. Yes, I do agree DERBY is very easy to use
and get started.
I am looking for a solution more on the line of tsearch2
(http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A//www.sai.msu.su/%7Emegera/postgres/gist/tsearch/V2/&ei=zcUBQ9aGCYmm-gGPr9DcAg)
I guess all we ne
