Lucene's test for multi-valued fields is crude... it's essentially if the number of values (un-inverted term instances) becomes greater than the number of documents.
-Yonik http://www.lucidimagination.com On Tue, Oct 6, 2009 at 3:04 PM, wojtekpia <wojte...@hotmail.com> wrote: > > Hi, > > I'm running Solr version 1.3.0.2009.07.08.08.05.45 in 2 environments. I have > a field defined as: > > <field name="myDate" type="date" indexed="true" stored="true" > multiValued="true"/> > > The two environments have different data, but both have single and multi > valued entries for myDate. > > On one environment sorting by myDate works (sort seems to be by the 'last' > value if multi valued). > > On the other environment I get: > HTTP Status 500 - there are more terms than documents in field "myDate", but > it's impossible to sort on tokenized fields java.lang.RuntimeException: > there are more terms than documents in field > > I've read that I shouldn'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. > >
