On Mon, Jan 23, 2012 at 11:31 PM, Jamie wrote:
> Ian
>
> Thanks. I'll have to read up about it. I have a lot of comparisons to make,
> so cannot precompute the values.
How many is a lot? If it were 100 or so I would still be tempted to do
all 4,950 comparisons and find some sensible way to store
> ...
> Don't you think this would be a nice feature for Lucene?
Can't say I've ever missed it, and haven't noticed others asking for
it. You need to remember that lucene is not a database.
> The Lucene query syntax has not changed much over the past few years. Are
> there any plans to broaden i
Ian
Thanks. I'll have to read up about it. I have a lot of comparisons to
make, so cannot precompute the values.
Don't you think this would be a nice feature for Lucene?
The Lucene query syntax has not changed much over the past few years.
Are there any plans to broaden its capabilities?
J
I guess you could do it in a custom Collector. They get passed
readers and docids so you could do the lookups and comparison. There
will be performance implications that you may be able to minimise via
FieldCache.
Storing the result in the index sounds much more sensible.
--
Ian.
On Mon, Jan
Hi Everyone
I have a problem where I need to compare two indexed fields as part of a
query.
For instance: modified_date[1970 to 2012] AND NOT deleted_date>modified_date
how would one implement this using Lucene?
Bear in mind, I need a dynamic way of accomplishing this comparison.
In my case
