lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doron Cohen <cdor...@gmail.com>
Subject Re: Why is CustomScoreQuery limited to ValueSourceQuery type?
Date Wed, 22 Apr 2009 21:26:12 GMT
Steve, I added a patch in https://issues.apache.org/jira/browse/LUCENE-1608,

which allows to wrap any query in a value source, and then create a value
source query out of it.
Let us know how this works for you...
Doron

On Wed, Apr 22, 2009 at 2:07 AM, Steven Bethard <bethard@stanford.edu>wrote:

> On 4/21/2009 10:09 AM, Doron Cohen wrote:
> > It could, but (historically and) currently it doesn't... :)
> > I actually have code for this.
> > Would you like open a JIRA issue for this - I'll attach my wrapper there?
>
> Done.
>
> https://issues.apache.org/jira/browse/LUCENE-1608
>
> Steve
>
> > On Tue, Apr 21, 2009 at 7:58 PM, Steven Bethard <bethard@stanford.edu
> >wrote:
> >
> >> On 4/21/2009 12:47 AM, Doron Cohen wrote:
> >>> CustomScoreQuery expects the VSQs to have a score for document matching
> >> the
> >>> (main) subQuery - this does not hold for arbitrary queries.
> >> Sure, but it could easily assign 0.0 scores for sub-queries that didn't
> >> match, no?
> >>
> >> Steve
> >>
> >>> On Sat, Apr 18, 2009 at 2:35 AM, Steven Bethard <bethard@stanford.edu
> >>> wrote:
> >>>
> >>>> CustomScoreQuery only allows the secondary queries to be of type
> >>>> ValueSourceQuery instead of allowing them to be any type of Query. Why
> >>>> is that? Is there something that makes it hard to implement for
> >>>> arbitrary queries?
> >>>>
> >>>> Steve
> >>>>
> >>>> P.S. I played around with this briefly, and simply replacing all
> >>>> ValueSourceQuery references with Query references yields only one
> simple
> >>>> compile error, where ValueSourceQuery.createWeight() is being used
> >>>> instead of Query.weight() for some reason.
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message