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 Wed, 14 Dec 2011 00:01:30 GMT


Yonik Seeley commented on SOLR-2950:

It would probably be most performant to do the lookup perSegment (i.e. in setNextReader) and
remove documents as they are found (i.e. if the doc exists in segment1, don't bother looking
it up in further segments).  This will also mean that we only do hash lookups in the SentinelIntSet
when there actually exists a boosted doc in the segment.
> QueryElevationComponent needlessly looks up document ids
> --------------------------------------------------------
>                 Key: SOLR-2950
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: 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