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:23:47 GMT


Chris Male commented on LUCENE-2883:

So the goal here is to make the top-level searcher (IR) visible to the
FQ's getValues? I think this pre-dated the cutover to
AtomicReaderContext, which now provides the top reader? Maybe this
isn't needed anymore...?

Its very intentional (as Yonik has pointed out).  It allows any Querys in the ValueSources
to be weighted.

Though QueryValueSource needs a searcher (but, seems to make one, from
the top reader, if it wasn't provided one).

Is this desirable? IndexSearcher is pretty thin I know but is it fast enough to create that
it has a nominal effect? If its faster than passing down the IndexSearcher then maybe its
a good idea for anybody wanting an IndexSearcher to do this.

Good question... maybe we can do this on a branch?

Absolutely, can you create one?

> 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