Re: sort by price puts unknown prices first

2011-03-02 Thread Yonik Seeley
On Wed, Mar 2, 2011 at 4:19 PM, Scott K wrote: > On Wed, Mar 2, 2011 at 12:21, Chris Hostetter > 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)

Re: sort by price puts unknown prices first

2011-03-02 Thread Scott K
On Wed, Mar 2, 2011 at 12:21, Chris Hostetter 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, t

Re: sort by price puts unknown prices first

2011-03-02 Thread Chris Hostetter
: When I sort by price ascending, documents with no price are listed : first. I would like them listed last. I tried adding the : sortMissingLast flag, even though it says it is only for strings, but it works for any field type *backed* by a string, including the SortableIntField (and it's breat

sort by price puts unknown prices first

2011-03-02 Thread Scott K
When I sort by price ascending, documents with no price are listed first. I would like them listed last. I tried adding the sortMissingLast flag, even though it says it is only for strings, but it did not help. Why doesn't sortMissingLast work on non-strings? This seems like a very common issue, bu