[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913712#action_12913712
]
Yonik Seeley edited comment on LUCENE-2649 at 9/22/10 2:46 PM:
---------------------------------------------------------------
bq. But we could probably still achieve these two benefits while using a single
class for looking up everything "cached" about a field? Ie, the CachedArray
could return non-null bits but null values?
Exactly.
And with NRT and increasing number of segments, the number of synchronized
lookups per segment could really start to matter.
was (Author: [email protected]):
bq. But we could probably still achieve these two benefits while using a
single class for looking up everything "cached" about a field? Ie, the
CachedArray could return non-null bits but null values?
Exactly.
And with NRT and increasing number of segments, the number of synchronized
lookups per second could really start to matter.
> FieldCache should include a BitSet for matching docs
> ----------------------------------------------------
>
> Key: LUCENE-2649
> URL: https://issues.apache.org/jira/browse/LUCENE-2649
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Fix For: 4.0
>
> Attachments: LUCENE-2649-FieldCacheWithBitSet.patch,
> LUCENE-2649-FieldCacheWithBitSet.patch,
> LUCENE-2649-FieldCacheWithBitSet.patch,
> LUCENE-2649-FieldCacheWithBitSet.patch, LUCENE-2649-FieldCacheWithBitSet.patch
>
>
> The FieldCache returns an array representing the values for each doc.
> However there is no way to know if the doc actually has a value.
> This should be changed to return an object representing the values *and* a
> BitSet for all valid docs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
