I tied almost all possible combination but in vain.
Does anyone know if there is any logic build in to suggester component to
ignore the leading numbers?
autocomplete?qt=/lucid&req_type=auto_complete&spellcheck.collate=false&q=34g
1
2
3
galaxy
/autocomplete?qt=/lucid&req_type=auto_com
Here’s a rather obvious question: have you rebuilt your spell index recently?
Is it possible the offending numbers snuck into the spell dictionary? The
terms component will show you what’s in your current, searchable field…but not
the dictionary.
If my memory serves correctly, with collate=t
Thanks a lot for your response Erik.
I was trying to find if I have any suggestion starting with numbers using
terms component but I couldn't find any.. Its very strange!!!
Anyways, thanks again for your response.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Autosu
Ah, OK, I though you were indexing things like 123412335ga, but not so.
Afraid I'm fresh out of ideas. Although I might try using TermsComponent
to examine the index and see if, somehow, there _are_ terms with leading
numbers in the output.
It's also possible that numbers are stripped when bu
Hi Erik,
Thanks a lot for your reply.
I expect it to return zero suggestions since the suggested keyword doesnt
actually start with numbers.
Expected results
Searching for ga -> returns galaxy
Searching for gal -> returns galaxy
Searching for 12321312321312ga -> should not return any suggestio
Hmmm, the example you post seems correct to me, the returned
suggestion is really close to the term. What are you expecting here?
The example is inconsistent with
"it returns the suggestion corresponding to the alphabets (ignoring the
numbers)"
It looks like it's considering the numbers just fine
