[
https://issues.apache.org/jira/browse/SOLR-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491092#comment-13491092
]
Robert Muir commented on SOLR-3855:
-----------------------------------
{quote}
If we allow for direct doc values, this makes sense to not load them by
default, but I think we should add documentation to the example schema.xml so
that people know that it is wasteful to store fields if doc values are enabled
and in memory, and that they can be added very easily to the response by adding
the field name to the fl parameter.
{quote}
just as wasteful as your example above: adding DocValues to a TrieIntField
right? By adding docvalues, its implying that its a single-valued field, and
you could do a DocValuesRangeQuery instead (works just like
FieldCacheRangeQuery), so why invert it too: wasting space in the postings
lists and term dictionary?
> DocValues support
> -----------------
>
> Key: SOLR-3855
> URL: https://issues.apache.org/jira/browse/SOLR-3855
> Project: Solr
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: 4.1, 5.0
>
> Attachments: SOLR-3855.patch
>
>
> It would be nice if Solr supported DocValues:
> - for ID fields (fewer disk seeks when running distributed search),
> - for sorting/faceting/function queries (faster warmup time than fieldcache),
> - better on-disk and in-memory efficiency (you can use packed impls).
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
