[
https://issues.apache.org/jira/browse/LUCENE-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13442711#comment-13442711
]
Robert Muir commented on LUCENE-4331:
-------------------------------------
maybe we could disambiguate this somehow with some wording like "this is
designed to be accessed in a column oriented way... and so aren't returned
by IR.document().... if you want to access it in a row/(document)-oriented way
for summary results you should also Store"
> XXXDocValuesField javadocs are confusing about storing
> ------------------------------------------------------
>
> Key: LUCENE-4331
> URL: https://issues.apache.org/jira/browse/LUCENE-4331
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> These all say:
> {quote}
> If you also need to store the value, you should add a
> separate {@link StoredField} instance.
> {quote}
> This is a little awkward. I can see how it makes sense in the (expert) case
> where you keep the DVs on disk, and you somehow need somethings as a DV for
> fast access, but also in summary results (so you dont seek to stored fields
> for the doc, and also to each DV field).
> But I'm not sure the current wording makes this less confusing: it would be
> nice to elaborate on this specific case, but in general if someone has dv
> fields loaded up with the default IR.docValues impl (which is a cached Source
> right?), then putting this crap in the stored fields does no good.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
