Good luck! You'll need it. Problem is this is such a sticky wicket. You can move the cleaning up to the PHP layer, that is strip out the parens.
You could write a Solr component that got the query _very_ early and transformed it. You'd have to get here before parsing. Either way, though, you'll be endlessly trying to second-guess the query parsing and/or intent of the user. I'd recommend the PHP layer if anything, it's closer to the user and you may have a better chance to guess right. Best, Erick On Wed, Feb 26, 2014 at 10:36 PM, deniz <denizdurmu...@gmail.com> wrote: > Hello, > > We are facing some kinda weird problem. So here is the scenario: > > We have a frontend and a middle-ware which is dealing with user input > search > queries before posting to Solr. > > So when a user enters city:Frankenthal_(Pfalz) and then searches, there is > no result although there are fields on some documents matching > city:Frankenthal_(Pfalz). We are aware that we can escape those chars, but > the middleware which is accepting queries is running on a Glassfish server, > which is refusing URLs with backslashes in it, hence using backslashes is > not okay for posting the query. > > To make everyone clear about the system it looks like: > > (PHP) -> Encoded JSON -> (Glassfish App - Middleware) -> Javabin -> Solr > > any other ideas who to deal with queries with special chars like this one? > > > > ----- > Zeki ama calismiyor... Calissa yapar... > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Searching-with-special-chars-tp4120047.html > Sent from the Solr - User mailing list archive at Nabble.com. >
