Thanks for helping out this user Hoss. I needed to highlight the ramifications of both the trie types and the impact of the ms() function on chapter 5 so I enhanced this addendum a bit more. I feel a little bad with "1.4" in the book title given the book came out before its release, but Packt basically required a version # and 1.4 made much more sense than 1.3.
The behavior the user sees shouldn't happen, IMO. When you're doing something that requires a field to be indexed with a single term (e.g. ord,rord, and others), instead of getting an error you get odd behavior. It's unfortunate. Perhaps I'll file a bug... a field would have to be declared to have no more than 1 token and features that require it would have to check. ~ David Smiley hossman wrote: > > > : My 'inspiration' for the ord method was actually the Solr 1.4 Enterprise > : Search server book. Page 126 has a section 'using reciprocals and rord > : with dates'. You should let those guys know what's up! > > 1) Although it's not 100% obvious, those examples in the book use the > "DateField" type -- and ord() should still work for those. If you are > using TrieDateField then things work differently. > > 2) David and EricP are regulars on the solr-user list, so rest assured > they already know. > > 3) There is a wiki page with an Addendum section they wrote to cover > things that changed in Solr prior to the 1.4 release but after they went > to press. Trie fields are mentioned, as is the new ms() function, but i > don't see anything explicitly addressing the snag you hit ... yet. It is > a wiki afterall, so you can feel free to add things as you find them. > > > > -Hoss > > > -- View this message in context: http://old.nabble.com/ord-on-TrieDateField-always-returning-max-tp27045931p27095782.html Sent from the Solr - User mailing list archive at Nabble.com.
