lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2950) QueryElevationComponent needlessly looks up document ids
Date Tue, 06 Dec 2011 15:51:42 GMT


Yonik Seeley commented on SOLR-2950:

Instead of doing everything on inform (which isn't great for NRT), we should just do it on-demand
in the comparator in setNextReader() for only those uniqueKeys that were boosted)

We could cache the uniqueKey -> docid across queries, but not sure it's worth it at this
point (assuming at most a handful of docs are boosted per-query).  And if we did want some
sort of uniqueKey -> docid cache it would make most sense to be an internal cache in SolrIndexSearcher,
not private to the QEC.
> QueryElevationComponent needlessly looks up document ids
> --------------------------------------------------------
>                 Key: SOLR-2950
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Priority: Minor
>             Fix For: 3.6, 4.0
> The QueryElevationComponent needlessly instantiates a FieldCache and does look ups in
it for every document.  If we flipped things around a bit and got Lucene internal doc ids
on inform() we could then simply do a much smaller and faster lookup during the sort.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message