On Wed, Mar 2, 2011 at 12:21, Chris Hostetter <hossman_luc...@fucit.org> wrote: > historicly it has been because of a fundemental limitation in how the > Lucene FieldCache has historicly worked where the array backed FieldCaches > use the default numeric value (ie: 0) when docs have no value (but in the > case of Strings, the default is "null" which is easy to test for) > > i am 99.99% certain this has changed on the trunk, so all of the > Trie*Fields should support the sortMissing* options in 4.x
I am running a 4.x build and just tried the most recent nightly build, apache-solr-4.0-2011-03-02_08-06-07.tgz, and am still seeing this issue. Other than creating a new indexed field where I manually map no value to a high number, is there a way to sort on a function query that puts undefined values to the end? Is there no way to use map to change undefined values? Thanks, Scott
