lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] Commented: (SOLR-1111) fix FieldCache usage in Solr
Date Mon, 13 Apr 2009 14:31:15 GMT


Yonik Seeley commented on SOLR-1111:

The major issue is that Lucene now creates scorers per-segment, and if you use Lucene's,sort)
then the FieldCache populations will also be per-segment.

The biggest issue:  If FieldCache get's populated at both the top-level reader and per-segment,
memory usage doubles (as does un-inversion time).
 - Faceting on single-valued fields uses the FieldCache at the top-level (and would be
   - This is non-trivial to change...  if we started counting per-segment, counts would somehow
have to be merged across segments.
 - Sorting in Solr currently uses the FieldCache at the top level
   - This can't easily be changed to use Lucene's,sort) since we are using
a hit collector (which can be wrapped in a time limited collector).
 - Distributed search uses the top-level FieldCache to retrieve sort field values.
 - FunctionQuery now derives values at the segment level
   - This also applies to the function range query

> fix FieldCache usage in Solr
> ----------------------------
>                 Key: SOLR-1111
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Yonik Seeley
>             Fix For: 1.4
> Recent changes in Lucene have altered how the FieldCache is used and as-is could lead
to previously working Solr installations blowing up when they upgrade to 1.4.  We need to
fix, or document the affects of these changes.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message