[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910568#action_12910568
]
Simon Willnauer commented on LUCENE-2649:
-----------------------------------------
bp. Perhaps FieldCache.Parser was originally just too narrow in scope - it
should have been a factory method for handling all decisions about creating and
populating a field cache entry?
I guess we need to be able to manually configure FieldCache with some kind of
FieldType. There have been several issues mentioning this and it keeps coming
up again and again. I think it is just time to rethink Fieldable / Field and
move towards some kind of flexible type definition for Fields in Lucene. A
FieldType could then have a FieldCache Attribute which contains all necessary
info including the parser and flags like the one we are talking about. Yet,
before I get too excieted about FieldType, yeah something with a wider scope
than FieldCache.Parser would work in this case. I don't know how far the
FieldType is away but it can eventually replace whatever is going to be
implemented here in regards to that flag.
I think by default we should not enable the Bits feature but it must be
explicitly set via whatever mechanism we gonna use.
> 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
>
>
> 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]
