lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-7878) Use SortedNumericDocValues (efficient sort & facet on multi-valued numeric fields)
Date Tue, 11 Aug 2015 23:15:45 GMT

    [ https://issues.apache.org/jira/browse/SOLR-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692461#comment-14692461
] 

Hoss Man commented on SOLR-7878:
--------------------------------

bq. ...and today multi-valued sorting isn't directly possible.

Can you explain what you mean by that?

With SOLR-2522 + LUCENE-6609 you can do things like: {{sort=field(multi_valued_numeric_field,min)+asc}}
and it directly uses SortedSetSortField under the covers. (although it's admittedly very new
so you may have just overlooked that it was recently added ... like a day before you opened
this jira :) )

NOTE: i agree, it would be nice to figure out a way to move towards SortedNumericDocValues,
and/or maybe even Mike's cool work in LUCENE-6697, i just want to clarify whether this would
purely be about optimizing current performance and minimizing code complexity, or if there
is some actual functionality of SortedNumericDocValues that you know we are currently missing
out on that i'm not aware of.

> 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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message