jamie at stimulussoft
Jan 23, 2012, 4:31 AM
Post #3 of 5
(167 views)
Permalink
|
|
Re: comparing index fields within a query
[In reply to]
|
|
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?
Jamie
On 2012/01/23 2:21 PM, Ian Lea wrote:
> 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 23, 2012 at 10:33 AM, Jamie<jamie [at] stimulussoft> wrote:
>> 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, it is not possible to store the result of
>> deleted_date>modified_date at the time of indexing.
>>
>> Thanks
>>
>> Jamie
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe [at] lucene
>> For additional commands, e-mail: java-user-help [at] lucene
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe [at] lucene
> For additional commands, e-mail: java-user-help [at] lucene
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe [at] lucene
For additional commands, e-mail: java-user-help [at] lucene
|
