[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910736#action_12910736
]
Yonik Seeley commented on LUCENE-2649:
--------------------------------------
bq. What if I care, but somethign else (that does not care) asks for the value
first? Seems odd to have so much depend on who asks for the value first
As long as it *can* be passed everywhere that matters, then it's up to the
application - which knows if it ever needs the missing values or not for that
field. For solr, we could make it configurable per-field... but I'd prob
default it to ON to avoid unpredictable weirdness.
bq. What if a filter creates the cache before the SortField?
If we have a filter that uses the field cache, then it should also be able to
specify the same stuff that SortField can.
> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
