lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1608) CustomScoreQuery should support arbitrary Queries
Date Wed, 22 Apr 2009 21:10:47 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701683#action_12701683
] 

Doron Cohen commented on LUCENE-1608:
-------------------------------------

I thought I had written a class exactly for this purpose but I was wrong - my class was different
in that it had an actual value source, just that it was sparse - values for quite many docs
were missing. It is similar in a way, but different since here the input is a query.

But I did promise... so I wrote a quick wrapper for a query to create a value source.
That value source can be used to create a value source query.

Although the patch coming soon is tested and all, I am not considering to commit this patch,
because it is not clean. 

I would like to reorganize this package to take better care of this request and other related
issues (like LUCENE-850) and to make it worth for Solr to move to use this package. (last
time I checked it wasn't). But this is a different issue...

> CustomScoreQuery should support arbitrary Queries
> -------------------------------------------------
>
>                 Key: LUCENE-1608
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1608
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Query/Scoring
>            Reporter: Steven Bethard
>            Assignee: Doron Cohen
>            Priority: Minor
>
> CustomScoreQuery only allows the secondary queries to be of type ValueSourceQuery instead
of allowing them to be any type of Query. As a result, what you can do with CustomScoreQuery
is pretty limited.
> It would be nice to extend CustomScoreQuery to allow arbitrary Query objects. Most of
the code should stay about the same, though a little more care would need to be taken in CustomScorer.score()
to use 0.0 when the sub-scorer does not produce a score for the current document.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message