[
https://issues.apache.org/jira/browse/SOLR-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049982#comment-16049982
]
Hoss Man commented on SOLR-7878:
--------------------------------
Again: I'm not that familar with the code (and again: i feel like these
questions/conversation belongs in SOLR-9989 since it's specific to JSON
Faceting) so if you think a wrapper that emulates SorterSetDocValues is the
best approach then go for it -- i was just surprised given that seems like it
would involve a lot of redundent LegacyNumeric conversion.
but on the flip side: if it seems like the most straight forward approach, then
we can always go with that for now and try to optimize later.
> 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: [email protected]
For additional commands, e-mail: [email protected]
