Brackets are range operators for the parser, you need to escape them \[ or
enclose in quotes.
On Apr 29, 2015 10:27 PM, "Kaushik" wrote:
> Hi Roman,
>
> "Tween 20" also did not retrieve me results. So I replaced the whitespaces
> in the synonyms.txt with 'x' and now when I search, I get the resu
Hi Roman,
"Tween 20" also did not retrieve me results. So I replaced the whitespaces
in the synonyms.txt with 'x' and now when I search, I get the results back.
One problem however still exits. i.e. when I search for POLYSORBATE
20[MART.] which is a synonym for POLYSORBATE 20, I get error as below
Hi Kaushik, I meant to compare tween 20 against "tween 20".
Your autophrase filter replaces whitespace with x, but your synonym filter
expects whitespaces. Try that.
Roman
On Apr 29, 2015 2:27 PM, "Kaushik" wrote:
> Hi Roman,
>
> When I used the debugQuery using
>
> http://localhost:8983/solr/c
Hi Roman,
When I used the debugQuery using
http://localhost:8983/solr/collection1/autophrase?q=tween+20&wt=json&indent=true&debugQuery=true
I see the following in the response. The autophrase plugin seems to be
doing its part. Just not the synonym expansion. When you say use phrase
queries, what d
Pls post output of the request with debugQuery=true
Do you see the synonyms being expanded? Probably not.
You can go to the administer iface, in the analyzer section play with the
input until you see the synonyms. Use phrase queries too. That will be
helpful to elliminate autophrase filter
On Apr
Hi Roman,
Following is my use case:
*Schema.xml*...
*SolrConfig.xml...*
name="/autophrase" class="solr.SearchHandler">
explicit
10
name
autophrasingPa
I'm not sure I understand - the autophrasing filter will allow the
parser to see all the tokens, so that they can be parsed (and
multi-token synonyms) identified. So if you are using the same
analyzer at query and index time, they should be able to see the same
stuff.
are you using multi-token syn
Hi there,
I tried the solution provided in
https://lucidworks.com/blog/solution-for-multi-term-synonyms-in-lucenesolr-using-the-auto-phrasing-tokenfilter/
.The mentioned solution works when the indexed data does not have alpha
numerics or special characters. But in my case the synonyms are someth
Handling MESH descriptor preferred terms and such is similar. I encountered
this during evaluation of Solr for a project here at NLM. We decided to use
Solr for different projects instead. I considered the following approaches:
- use a custom tokenizer at index time that indexed all of t
