[SOLR-2339] No error reported when sorting on a multiValued field

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1, 4.0-ALPHA
• Component/s: search
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 28/Jan/11 02:04
• Updated: 17/May/11 01:58
• Resolved: 04/Feb/11 00:11

Description

In the past, Solr has relied on the underlying FieldCache to throw an error in situations where sorting on a field was not possible. however LUCENE-2142 has changed this, so that FieldCache never throws an error.

In order to maintain the functionality of past Solr releases (ie: error when users attempt to sort on a field that we known will produce meaningless results) we should add some sort of check at the Solr level.

Issue Links

• is broken by: LUCENE-2142 FieldCache.getStringIndex should not throw exception if term count exceeds doc count
• relates to: SOLR-2249 ArrayIndexOutOfBoundsException thrown instead of useful FieldCache exception when too many terms
• relates to: SOLR-2348 No error reported when using a FieldCached backed ValueSource for a field Solr knows won't work
• requires: SOLR-2522 add syntax for selecting the min or max of a multivalued field in value source functions