hi jack,
It worked with dismax. I was using a our search partner provided wrapper
around dismax and it seems like it has a bug.
I switched to dismax and all is working fine now.
Thanks for help
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
hi jack,
thanks, i figured out the issue. It was settings during query and index time
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time
hi jack,
thanks, i figured out the issue. It was settings during query and index time
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951811.html
Sent from the Solr - User mailing list archive at Nabble.com.
onday, April 30, 2012 11:56 AM
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabbl
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951083.html
Sent from the Solr - User mailing list archive at Nabbl
hi jack,
tried &qs=10 but unfortunately it does not seem to help.
Not sure what else could be wrong
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951082.html
Sent from the Solr - User mailing list archive at Nabbl
hi jack & erick,
Thanks
I do have qs set in solrconfig for query handler dismax settings.
10
Still does not work
abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/solr-WordDelimiterFilterFactory-query-time-tp3950045p3951038.html
Sent from the Solr - User mailing list a
The &qs=1 request parameter should work for the dismax query parser as well
as edismax.
-- Jack Krupansky
-Original Message-
From: Erick Erickson
Sent: Monday, April 30, 2012 10:58 AM
To: solr-user@lucene.apache.org
Subject: Re: solr.WordDelimiterFilterFactory query time
See Ja
See Jack's comments about phrases, all your parsed
queries are phrases, and your indexed terms aren't
next to each other.
Best
Erick
On Mon, Apr 30, 2012 at 10:54 AM, abhayd wrote:
> hi Erick,
> autoGeneratePhraseQueries="false" is set for field type. And it works fine
> for standard query parse
hi Erick,
autoGeneratePhraseQueries="false" is set for field type. And it works fine
for standard query parser.
Problem seem to be when i start using dismax. As u suggested i checked
analysis tool and even after word delimiter is applied i see search term as
"blackberry 9801" so i dont think it s
When WDF filters blackberry9810 it will treat it as a sequence of tokens but
as if it were a phrase, like "blackberry 9810", with the two terms adjacent,
at least with the edismax query parser. I'm not sure what the other query
parsers do.
If you are using edismax, you can set the QS (query sl
Try attaching &debugQuery=on to your query and seeing if that helps
you understand what's going on. If that doesn't help, also look at
admin/analysis. If all that doesn't help, post your schema definition
for the field type and the results of &debugQuery=on (you might
look at: http://wiki.apache.or
12 matches
Mail list logo
