[
https://issues.apache.org/jira/browse/SOLR-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049925#comment-16049925
]
Cao Manh Dat edited comment on SOLR-7878 at 6/15/17 3:23 AM:
-------------------------------------------------------------
[~hossman] I am thinking about that direction too. But "terms" in json facet
kinda relates too TermsEnum ( the values must be global sorted ), right? But
SortedNumericDV is a mapping from docId -> list of values. It do not have
reverse direction.
was (Author: caomanhdat):
[~hossman] I am thinking about that direction too. But "terms" in json facet
kinda relates too TermsEnum, right? But SortedNumericDV is a mapping from docId
-> list of values. It do not have reverse direction.
> Use SortedNumericDocValues (efficient sort & facet on multi-valued numeric
> fields)
> ----------------------------------------------------------------------------------
>
> Key: SOLR-7878
> URL: https://issues.apache.org/jira/browse/SOLR-7878
> Project: Solr
> Issue Type: Improvement
> Components: Facet Module
> Reporter: David Smiley
>
> Lucene has a SortedNumericDocValues (i.e. multi-valued numeric DocValues),
> ever since late in the 4x versions. Solr's TrieField.createFields
> unfortunately still uses SortedSetDocValues for the multi-valued case.
> SortedNumericDocValues is more efficient than SortedSetDocValues; for example
> there is no 'ordinal' mapping for sorting/faceting needed.
> Unfortunately, updating Solr here would be quite a bit of work, since there
> are backwards-compatibility concerns, and faceting code would need a new code
> path implementation just for this. Sorting is relatively simple thanks to
> SortedNumericSortField, and today multi-valued sorting isn't directly
> possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
