[
https://issues.apache.org/jira/browse/LUCENE-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036633#comment-13036633
]
Chris Male commented on LUCENE-2883:
------------------------------------
Hey Yonik,
Its super to hear from you on this, it'll be a real help.
{quote}
Regarding weighting - function queries can contain normal queries, so anywhere
a function query is used, it must be weighted first.
{quote}
Yup I've come to understand that. So the challenge is how to do this when a
FunctionQuery is used to sort and not Query? Okay. I'm going to open an issue
to see if we can address this better, maybe by extending SortField or something.
{quote}
Sort instances are like Query instances, and for many reasons should not be
bound to any particular searcher.
{quote}
Yeah that is true. But ValueSource#getSort actually returns a SortField. Does
the same apply to SortField instances? Also, ValueSource#weight(IndexSearcher)
returns a new SortField as well, with a context containing the IndexSearcher.
Consequently the new SortField is bound to that particular searcher.
> Consolidate Solr & Lucene FunctionQuery into modules
> -----------------------------------------------------
>
> Key: LUCENE-2883
> URL: https://issues.apache.org/jira/browse/LUCENE-2883
> Project: Lucene - Java
> Issue Type: Task
> Components: core/search
> Affects Versions: 4.0
> Reporter: Simon Willnauer
> Labels: gsoc2011, lucene-gsoc-11, mentor
> Fix For: 4.0
>
> Attachments: LUCENE-2883.patch
>
>
> Spin-off from the [dev list |
> http://www.mail-archive.com/[email protected]/msg13261.html]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
