Re: Different sort behavior on same code

t sort by multi-valued fields, so my solution will >>> be to add a single-valued date field for sorting. But I don't understand why >>> my two environments behave differently, and it doesn't seem like the error >>> message makes sense (are date fields tokenized?). Any thoughts? >>> >>> Thanks, >>> >>> Wojtek >>> -- >>> View this message in context: >>> http://www.nabble.com/Different-sort-behavior-on-same-code-tp25774769p25774769.html >>> Sent from the Solr - User mailing list archive at Nabble.com. >>> >>> >> > > > > -- > Lance Norskog > goks...@gmail.com >

Re: Different sort behavior on same code

sorting. But I don't understand why >> my two environments behave differently, and it doesn't seem like the error >> message makes sense (are date fields tokenized?). Any thoughts? >> >> Thanks, >> >> Wojtek >> -- >> View this message in context: >> http://www.nabble.com/Different-sort-behavior-on-same-code-tp25774769p25774769.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >> > -- Lance Norskog goks...@gmail.com

Re: Different sort behavior on same code

;t seem like the error > message makes sense (are date fields tokenized?). Any thoughts? > > Thanks, > > Wojtek > -- > View this message in context: > http://www.nabble.com/Different-sort-behavior-on-same-code-tp25774769p25774769.html > Sent from the Solr - User mailing list archive at Nabble.com. > >

Different sort behavior on same code

s, Wojtek -- View this message in context: http://www.nabble.com/Different-sort-behavior-on-same-code-tp25774769p25774769.html Sent from the Solr - User mailing list archive at Nabble.com.