[
https://issues.apache.org/jira/browse/SOLR-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765228#action_12765228
]
Yonik Seeley commented on SOLR-1508:
------------------------------------
IndexReader has getSequentialSubreaders(), and I think in Lucene trunk the
offsets and readers are also available from IndexSearcher. SolrIndexReader also
gives you access to the list of offsets and subreaders. But the lucene part of
this is easy... as usual, the hard part is good interfaces and integration...
coming up with the right way to express it all.
This also seems like it could be related to SOLR-1298... one should be able to
return the value of any arbitrary function (even those of non-indexed fields
such as ExternalFileField), not just the straight field value.
Other things to think about:
- how does this fit in with proposed interfaces that let one store "stored
fields" somewhere else, like a DB?
- how does this fit in with future column stored fields? future payload stored
fields?
- if a field is stored and indexed, and a user requests the complete document,
what do we use for the FieldCache field?
- multi-valued support using UnInvertedField?
- fl=*, does it select all of these fields, or does one have to explicitly ask?
- how to distinguish a field that has a value from one that doesn't (not all
FieldCache entries can tell you this)
Anyway, my main suggestion is that we start with the hard part - the interfaces
(proposed HTTP args, schema.xml markup, etc)
> Use field cache when creating response, if available and configured.
> --------------------------------------------------------------------
>
> Key: SOLR-1508
> URL: https://issues.apache.org/jira/browse/SOLR-1508
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.3
> Reporter: Tom Hill
>
> Allow the user to configure a field to be returned to the user from the field
> cache, instead of getting the field from disk. Relies on lucene-1981
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
