lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (JIRA)" <>
Subject [jira] [Commented] (LUCENE-2883) Consolidate Solr & Lucene FunctionQuery into modules
Date Fri, 20 May 2011 02:35:47 GMT


Chris Male commented on LUCENE-2883:

Hey Yonik,

Its super to hear from you on this, it'll be a real help.

Regarding weighting - function queries can contain normal queries, so anywhere a function
query is used, it must be weighted first.

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.

Sort instances are like Query instances, and for many reasons should not be bound to any particular

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:
>             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 |]

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message