lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tushar kapoor <tushar_kapoor...@rediffmail.com>
Subject Re: Encoded search string & qt=Dismax
Date Wed, 03 Dec 2008 17:10:14 GMT

Hoss,

If the way I am doing it (Query 1) is a fluke, what is the correct way of
doing it? Seems like there is something fundamental that I am missing.

It would be great if you could list down the steps required to support multi
language search. Please provide some context on how exactly Language
analyzers are used.

I am attaching - 

http://www.nabble.com/file/p20817191/schema.xml schema.xml 
http://www.nabble.com/file/p20817191/solrconfig.xml solrconfig.xml 

Also, I am using a multicore setup with support for only one language per
core.
The field type on which I have applied language analyzer(Russian) is "text".

Regards,
Tushar.


hossman wrote:
> 
> 
> First of all...
> 
> standard request handler uses the default search field specified in your 
> schema.xml -- dismax does not.  dismax looks at the "qf" param to decide 
> which fields to search for the "q" param.  if you started with the example 
> schema the dismax handler may have a default value for "qf" which is 
> trying to query different fields then you actaully use in your documents.
> 
> &debugQuery=true will show you exactly what query structure (and on which 
> fields) each request is using.
> 
> Second...
> 
> I don't know Russian, and character encoding issues tend to make my head 
> spin, but the fact that the responseHeader is echoing back a q param 
> containing java string literal sequences suggests that you are doing 
> soemthing wrong.  you should be sending the URL encoding of the actaul 
> characters, not the URL encoding of the actual Russian word, not the URL 
> encoding or the java string literal encoding of the Russian word.  I 
> suspect the fact that you are getting any results at all from your first 
> query is a fluke.
> 
> The <str name="q"> in the responseHeader should show you the real word you 
> want to search for -- once it does, then you'll know that you have the 
> URL+UTF8 encoding issues straightened out.  *THEN* i would worry about the 
> dismax/standard behavior.
> 
> :  <lst name="params">
> :   <str
> :
> name="q">\u041f\u0440\u0435\u0434\u0432\u0430\u0440\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0435</str>

> :   </lst>
> 
> 
> -Hoss
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Encoded--search-string---qt%3DDismax-tp20797703p20817191.html
Sent from the Solr - User mailing list archive at Nabble.com.


Mime
View raw message