Thanks very much for your advice. I think I now better understand how to
make better use of solr. I have tested spellchecker and it looks like it let
me to achieve better results and hopefully we will satisfy the client.
In my solution I will change user query to use or not to use phonetic fields
I think Sujit has hit the nail on the head. Any program you try to write
that tries to guess what the user *really* meant will require endless
tinkering and *still* won't be right. If you only knew how annoying I
find Google's attempts to "help".
So perhaps concentrating on some interaction wi
Would it make sense to have a "Did you mean?" type of functionality for
which you use the EdgeNGram and Metaphone filters /if/ you don't get
appropriate results for the user query?
So when user types "cannon" and the application notices that there are
no cannons for sale in the index (0 results wi
Thanks for reply. I know that sometimes meeting all clients needs would be
impossible but then client recalls that competitive (commercial) product
already do that (but has other problems, like performance). And then I'm
obligated to try more tricks. :/
I'm currently using Solr 3.1 but thinking ab
The root problem here is "This is unacceptable for my client". The first
thing I'd suggest is that you work with your client and get them to define
what is acceptable. You'll be forever changing things (to no good purpose)
if all they can say is "that's not right".
For instance, you apparently hav
Hi all,
I have a database of e-commerce products (5M) and trying to build a search
solution for it.
I have used steemer, edgengram and doublemetaphone phonetic fields for
omiting common typos in queries. It works quite good with dismax QParser
for queries longer than one word: "tv lc20", "sny ps
