![]() I'm sure this can be done with this, but not sure how to do it exactly using suggester component provided in Solr and specifically which one lookup should I select to achieve this kind of suggestions. Just to clarify that by order by popularity I mean to list suggested terms by the number of times it is used by actual users to search, and not the one that would give more numbers of items as results. Instead it might just not provide suggestions if there is no suggestion, or provide those that are only in these categories. We also need to filter for parent category, so when someone select baby products as category, it would not list xperia play or xperia u for xpe.where the suggestions are specific product name. completing the full product name when someone writes it "xperia u", it should list xperia u android mobile phone - white, xperia u android mobile phone - black.For more complete term "xperia u" it should return xperia u, xperia u unlocked, xperia u case, xperia u st25i, etc.This can be popular searches listed as per their order by popularity. For the same term it should also return xperia ray, xperia arc, xperia play, etc.Auto suggest with term completion, like when I type "xpe" the suggester should return, xperia, xperia in Electronics, xperia in PCs & Laptops (this can be suggested term in category).This parameter specifies the query to spellcheck. This is required if spell checking is desired. If true, then spelling suggestions will be generated. spellcheck This parameter turns on SpellCheck suggestions for the request. ![]() I need to deploy a suggester similar to, Flipkart, NewEgg with following specific requirements: The SpellCheck component accepts the parameters described below. Solr 3.6+Ĭan you please help me understand this? Or help me decide which one is suitable for my requirements? WFSTLookup - weighted automaton representation: an alternative to FSTLookup for more fine-grained ranking. TSTLookup - ternary tree based representation, capable of immediate data structure updates,įSTLookup - automaton based representation slower to build, but consumes far less memory at runtime (see performance notes below). ![]() JaspellLookup - tree-based representation based on Jaspell, I have choose among these four Lookup Class: But I'm unable to decide which Lookup class should I use for Suggester, moreover there isn't any good documentation provided either from which I can find the best one. I've been referring to the Solr Suggester component () for the same. I'm working on Solr 3.6 for auto suggestions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |