Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException

2011-01-19 Thread Erick Erickson
There's nothing that I know of that would accomplish this, sorry... Best Erick On Tue, Jan 18, 2011 at 11:22 PM, kun xiong wrote: > Hi Erick, > Thanks for the fast reply. I kind of figured it was not supposed to be > that way. > But it would have some benefits when we need migrate from Lucene

Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException

2011-01-18 Thread kun xiong
Hi Erick, Thanks for the fast reply. I kind of figured it was not supposed to be that way. But it would have some benefits when we need migrate from Lucene to Solr. We don't have to rewrite the build query part, right. Is there any parser can do that? 2011/1/18 Ahmet Arslan > > what's the alte

Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException

2011-01-18 Thread Ahmet Arslan
> what's the alternative? q=kfc+mdc&defType=dismax&mm=1&qf=I_NAME_ENUM See more: http://wiki.apache.org/solr/DisMaxQParserPlugin

Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException

2011-01-18 Thread Tri Nguyen
what's the alternative? --- On Tue, 1/18/11, Erick Erickson wrote: From: Erick Erickson Subject: Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException To: solr-user@lucene.apache.org Date: Tuesday, January 18, 2011, 5:24 AM Why do you want to do this? Because toString has

Re: HTTP Status 400 - org.apache.lucene.queryParser.ParseException

2011-01-18 Thread Erick Erickson
Why do you want to do this? Because toString has never been guaranteed to be re-parsable, even in Lucene, so it's not surprising that taking a Lucene toString() clause and submitting it to Solr doesn't work. Best Erick On Tue, Jan 18, 2011 at 4:49 AM, kun xiong wrote: > -- Forwarded mes