: > Hmmmm.... good call, i didn't realize the escape method had been so : > blanket in 1.3. this way we protect people who were using it in 1.3 and : > relied on it to protect them from the legacy ";" behavior.
: Thanks hoss and ryan. That explains why the error was new to us-- we : upgraded to trunk from 1.3 release and this exception came from a solrj : processed query that used to work. I would still suggest you (and everybody else) always specify "sort" and "defType" params anyway (even if just as defaults in your requestHandler declaration), just to be very clear and complete about what you expect (and to ensure this weird legacy behavior doesn't burn you if clients who *aren't* using SolrJ (or ClientUtils) query your port. -Hoss
