Re: Re: Re: Re: Re: Query Autocomplete Evaluation
Paras, Thank you! This is all very helpful __ I'm going to read through your answer a couple more times and follow up if I have any more questions! Best, Audrey On 2/28/20, 8:08 AM, "Paras Lehana" wrote: Hey Audrey, Users often skip results and go straight to vanilla search even though > their query is displayed in the top of the suggestions list Yes, we do track this in another metric. This behaviour is more prevalent for shorter terms like "tea" and "bag". But, anyways, we measure MRR for quantifying how high are we able to show suggestions to the users. Since we include only the terms selection via Auto-Suggest in the universe for calculation, the searches where user skip Auto-Suggest won't be counted. I think we can safely exclude these if you're using MRR to measure how well you order your result set. Still, if you want to include those, you can always compare the search term with the last result set and include them in MRR - you're actually right that users maybe skipping the lower positions even if the intended suggestion is available. Our MRR stands at 68% and 75% of all of the suggestions are selected from position #1 or #2. So acceptance rate = # of suggestions taken / total queries issued? Yes. The total queries issues should ideally be those where Auto-Suggest was selected or could have been selected i.e. we exclude voice searches. We try to include as much as those searches which were made via typing in the search bar. But that's how we have fine-tuned our tracking over months. You're right about the general formula - searches via Auto-Suggest divided by total Searches. And Selection to Display = # of suggestions taken (this would only be 1, if > the not-taken suggestions are given 0s) / total suggestions displayed? If > the above is true, wouldn't Selection to Display be binary? I.e. it's > either 1/# of suggestions displayed (assuming this is a constant) or 0? Yup. Please note that this is calculated per session of Auto-Suggest. Let the formula be S/D. We will take D (Display) as 1 and not 3 when a user query for "bag" (b, ba, bag). If the S (Selection) was made in the last display, it is 1 also. If a user selects "bag" after writing "ba", we don't say that S=0, D=1 for "b" and S=1, D=1 for "ba". For this, we already track APL (Average Prefix Length). S/D is calculated per search and thus, here S=1, D=1 for search "bag". Thus, for a single search, S/D can be either 0 or 1 - you're right, it's binary! Hope this helps. Loved your questions! :) On Thu, 27 Feb 2020 at 22:21, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Paras, > > Thank you for this response! Yes, you are being clear __ > > Regarding the assumptions you make for MRR, do you have any research > papers to confirm that these user behaviors have been observed? I only ask > because this paper https://urldefense.proofpoint.com/v2/url?u=http-3A__yichang-2Dcs.com_yahoo_sigir14-5FSearchAssist.pdf=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=itCtsKdh-LT8eUwdVvqBc96lR_64mPtVw7t52WMtBLs=JrGARO4xkzWbtv7_b-H5da6Ki6PemYL5NQ253y0Y7Qs= > talks about how users often skip results and go straight to vanilla search > even though their query is displayed in the top of the suggestions list > (section 3.2 "QAC User Behavior Analysis"), among other behaviors that go > against general IR intuition. This is only one paper, of course, but it > seems that user research of QAC is hard to come by otherwise. > > So acceptance rate = # of suggestions taken / total queries issued ? > And Selection to Display = # of suggestions taken (this would only be 1, > if the not-taken suggestions are given 0s) / total suggestions displayed ? > > If the above is true, wouldn't Selection to Display be binary? I.e. it's > either 1/# of suggestions displayed (assuming this is a constant) or 0? > > Best, > Audrey > > > ____ > From: Paras Lehana > Sent: Thursday, February 27, 2020 2:58:25 AM > To: solr-user@lucene.apache.org > Subject: [EXTERNAL] Re: Re: Re: Query Autocomplete Evaluation > > Hi Audrey, > > For MRR, we assume that if a suggestion is selected, it's relevant. It's > also assumed that the user will always click the highest relevant > suggestion. Thus, we calculate position selection for each selection. If > still, I'm not understanding your question correctly, feel free to contact > me personally (hangouts?).
Re: Re: Re: Re: Query Autocomplete Evaluation
Hey Audrey, Users often skip results and go straight to vanilla search even though > their query is displayed in the top of the suggestions list Yes, we do track this in another metric. This behaviour is more prevalent for shorter terms like "tea" and "bag". But, anyways, we measure MRR for quantifying how high are we able to show suggestions to the users. Since we include only the terms selection via Auto-Suggest in the universe for calculation, the searches where user skip Auto-Suggest won't be counted. I think we can safely exclude these if you're using MRR to measure how well you order your result set. Still, if you want to include those, you can always compare the search term with the last result set and include them in MRR - you're actually right that users maybe skipping the lower positions even if the intended suggestion is available. Our MRR stands at 68% and 75% of all of the suggestions are selected from position #1 or #2. So acceptance rate = # of suggestions taken / total queries issued? Yes. The total queries issues should ideally be those where Auto-Suggest was selected or could have been selected i.e. we exclude voice searches. We try to include as much as those searches which were made via typing in the search bar. But that's how we have fine-tuned our tracking over months. You're right about the general formula - searches via Auto-Suggest divided by total Searches. And Selection to Display = # of suggestions taken (this would only be 1, if > the not-taken suggestions are given 0s) / total suggestions displayed? If > the above is true, wouldn't Selection to Display be binary? I.e. it's > either 1/# of suggestions displayed (assuming this is a constant) or 0? Yup. Please note that this is calculated per session of Auto-Suggest. Let the formula be S/D. We will take D (Display) as 1 and not 3 when a user query for "bag" (b, ba, bag). If the S (Selection) was made in the last display, it is 1 also. If a user selects "bag" after writing "ba", we don't say that S=0, D=1 for "b" and S=1, D=1 for "ba". For this, we already track APL (Average Prefix Length). S/D is calculated per search and thus, here S=1, D=1 for search "bag". Thus, for a single search, S/D can be either 0 or 1 - you're right, it's binary! Hope this helps. Loved your questions! :) On Thu, 27 Feb 2020 at 22:21, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Paras, > > Thank you for this response! Yes, you are being clear __ > > Regarding the assumptions you make for MRR, do you have any research > papers to confirm that these user behaviors have been observed? I only ask > because this paper http://yichang-cs.com/yahoo/sigir14_SearchAssist.pdf > talks about how users often skip results and go straight to vanilla search > even though their query is displayed in the top of the suggestions list > (section 3.2 "QAC User Behavior Analysis"), among other behaviors that go > against general IR intuition. This is only one paper, of course, but it > seems that user research of QAC is hard to come by otherwise. > > So acceptance rate = # of suggestions taken / total queries issued ? > And Selection to Display = # of suggestions taken (this would only be 1, > if the not-taken suggestions are given 0s) / total suggestions displayed ? > > If the above is true, wouldn't Selection to Display be binary? I.e. it's > either 1/# of suggestions displayed (assuming this is a constant) or 0? > > Best, > Audrey > > > ____ > From: Paras Lehana > Sent: Thursday, February 27, 2020 2:58:25 AM > To: solr-user@lucene.apache.org > Subject: [EXTERNAL] Re: Re: Re: Query Autocomplete Evaluation > > Hi Audrey, > > For MRR, we assume that if a suggestion is selected, it's relevant. It's > also assumed that the user will always click the highest relevant > suggestion. Thus, we calculate position selection for each selection. If > still, I'm not understanding your question correctly, feel free to contact > me personally (hangouts?). > > And @Paras, the third and fourth evaluation metrics you listed in your > > first reply seem the same to me. What is the difference between the two? > > > I was expecting you to ask this - I should have explained a bit more. > Acceptance Rate is the searches through Auto-Suggest for all Searches. > Whereas, value for Selection to Display is 1 if the Selection is made given > the suggestions were displayed otherwise 0. Here, the cases where results > are displayed is the universal set. Acceptance Rate is counted 0 even for > those searches where Selection was not made because there were no results > while S/D will not count this - it only counts cases where the result was > displayed. > > Hope I'm clear.
Re: Re: Re: Re: Query Autocomplete Evaluation
Paras, Thank you for this response! Yes, you are being clear __ Regarding the assumptions you make for MRR, do you have any research papers to confirm that these user behaviors have been observed? I only ask because this paper http://yichang-cs.com/yahoo/sigir14_SearchAssist.pdf talks about how users often skip results and go straight to vanilla search even though their query is displayed in the top of the suggestions list (section 3.2 "QAC User Behavior Analysis"), among other behaviors that go against general IR intuition. This is only one paper, of course, but it seems that user research of QAC is hard to come by otherwise. So acceptance rate = # of suggestions taken / total queries issued ? And Selection to Display = # of suggestions taken (this would only be 1, if the not-taken suggestions are given 0s) / total suggestions displayed ? If the above is true, wouldn't Selection to Display be binary? I.e. it's either 1/# of suggestions displayed (assuming this is a constant) or 0? Best, Audrey From: Paras Lehana Sent: Thursday, February 27, 2020 2:58:25 AM To: solr-user@lucene.apache.org Subject: [EXTERNAL] Re: Re: Re: Query Autocomplete Evaluation Hi Audrey, For MRR, we assume that if a suggestion is selected, it's relevant. It's also assumed that the user will always click the highest relevant suggestion. Thus, we calculate position selection for each selection. If still, I'm not understanding your question correctly, feel free to contact me personally (hangouts?). And @Paras, the third and fourth evaluation metrics you listed in your > first reply seem the same to me. What is the difference between the two? I was expecting you to ask this - I should have explained a bit more. Acceptance Rate is the searches through Auto-Suggest for all Searches. Whereas, value for Selection to Display is 1 if the Selection is made given the suggestions were displayed otherwise 0. Here, the cases where results are displayed is the universal set. Acceptance Rate is counted 0 even for those searches where Selection was not made because there were no results while S/D will not count this - it only counts cases where the result was displayed. Hope I'm clear. :) On Tue, 25 Feb 2020 at 21:10, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > This article > https://urldefense.proofpoint.com/v2/url?u=http-3A__wwwconference.org_proceedings_www2011_proceedings_p107.pdf=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=KMeOCffgJOgN3RoE0ht8jssgdO3AbyNYqRmXlQ6xWRo=fVp2mKYimlchSj0RMKpd595S7C2nGxK2G3CQSkrycg4= > also > indicates that MRR needs binary relevance labels, p. 114: "To this end, we > selected a random sample of 198 (query, context) pairs from the set of > 7,311 pairs, and manually tagged each of them as related (i.e., the query > is related to the context; 60% of the pairs) and unrelated (40% of the > pairs)." > > On 2/25/20, 10:25 AM, "Audrey Lorberfeld - audrey.lorberf...@ibm.com" < > audrey.lorberf...@ibm.com> wrote: > > Thank you, Walter & Paras! > > So, from the MRR equation, I was under the impression the suggestions > all needed a binary label (0,1) indicating relevance.* But it's great to > know that you guys use proxies for relevance, such as clicks. > > *The reason I think MRR has to have binary relevance labels is this > Wikipedia article: > https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_Mean-5Freciprocal-5Frank=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=1f2LPzuBvibQd8m-8_HuNVYFm0JvCGyPDul6r4ATsLk=Sn7KV-BcFDTrmc1PfRVeSpB9Ysh3UrVIQKcB3G5zstw= > , where it states below the formula that rank_i = "refers to the rank > position of the first relevant document for the i-th query." If the > suggestions are not labeled as relevant (0) or not relevant (1), then how > do you compute the rank of the first RELEVANT document? > > I'll check out these readings asap, thank you! > > And @Paras, the third and fourth evaluation metrics you listed in your > first reply seem the same to me. What is the difference between the two? > > Best, > Audrey > > On 2/25/20, 1:11 AM, "Walter Underwood" wrote: > > Here is a blog article with a worked example for MRR based on > customer clicks. > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__observer.wunderwood.org_2016_09_12_measuring-2Dsearch-2Drelevance-2Dwith-2Dmrr_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=e9a1kzjKu6l-P1g5agvpe-jQZfCF6bT4x6CeYDrUkgE=GzNrf4l_FjMqOkSx2B4_sCIGoJv2QYPbPqWplHGE3PI= > > At my place of work, we compare the CTR and MRR of queries using > suggestions to those that do not use suggestions. Solr autosuggest based on > lexicon of book ti
Re: Re: Re: Query Autocomplete Evaluation
> MRR = (B3+B4/2+B5/3+B6/4+B7/5+B8/6+B9/7+B10/8+B11/9+B12/10)/B13 > = 66.45% > > > > Refer here for MRR calculation keeping Auto-Suggest in > perspective: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__medium.com_-40dtunkelang_evaluating-2Dsearch-2Dmeasuring-2Dsearcher-2Dbehavior-2D5f8347619eb0=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=e9a1kzjKu6l-P1g5agvpe-jQZfCF6bT4x6CeYDrUkgE=WFv9xHoFHlnQmBgqIoHPi3moIiyttgAZJzWRxFLjyfk= > > > > "In practice, this is inverted to obtain the reciprocal rank, > e.g., if the > > searcher clicks on the 4th result, the reciprocal rank is 0.25. > The average > > of these reciprocal ranks is called the mean reciprocal rank > (MRR)." > > > > nDCG may require human intervention. Please let me know in case > I have not > > understood your question properly. :) > > > > > > > > On Mon, 24 Feb 2020 at 20:49, Audrey Lorberfeld - > audrey.lorberf...@ibm.com > > wrote: > > > >> Hi Paras, > >> > >> This is SO helpful, thank you. Quick question about your MRR > metric -- do > >> you have binary human judgements for your suggestions? If no, > how do you > >> label suggestions successful or not? > >> > >> Best, > >> Audrey > >> > >> On 2/24/20, 2:27 AM, "Paras Lehana" > wrote: > >> > >>Hi Audrey, > >> > >>I work for Auto-Suggest at IndiaMART. Although we don't use > the > >> Suggester > >>component, I think you need evaluation metrics for > Auto-Suggest as a > >>business product and not specifically for Solr Suggester > which is the > >>backend. We use edismax parser with EdgeNGrams Tokenization. > >> > >>Every week, as the property owner, I report around 500 > metrics. I would > >>like to mention a few of those: > >> > >> 1. MRR (Mean Reciprocal Rate): How high the user > selection was > >> among the > >> returned result. Ranges from 0 to 1, the higher the > better. > >> 2. APL (Average Prefix Length): Prefix is the query by > user. Lesser > >> the > >> better. This reports how less an average user has to type > for > >> getting the > >> intended suggestion. > >> 3. Acceptance Rate or Selection: How many of the total > searches are > >> being served from Auto-Suggest. We are around 50%. > >> 4. Selection to Display Ratio: Did you make the user to > click any > >> of the > >> suggestions if they are displayed? > >> 5. Response Time: How fast are you serving your average > query. > >> > >> > >>The Selection and Response Time are our main KPIs. We track > a lot about > >>Auto-Suggest usage on our platform which becomes apparent if > you > >> observe > >>the URL after clicking a suggestion on dir.indiamart.com. > However, not > >>everything would benefit you. Do let me know for any related > query or > >>explanation. Hope this helps. :) > >> > >>On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - > >> audrey.lorberf...@ibm.com > >> wrote: > >> > >>> Hi all, > >>> > >>> How do you all evaluate the success of your query autocomplete > (i.e. > >>> suggester) component if you use it? > >>> > >>> We cannot use MRR for various reasons (I can go into them if > you're > >>> interested), so we're thinking of using nDCG since we already > use > >> that for > >>> relevance eval of our system as a whole. I am also interested > in the > >> metric > >>> "success at top-k," but I can't find any research papers that > >> explicitly > >>> define "success" -- I am assuming it's a suggestion (or > suggestions) >
Re: Re: Re: Query Autocomplete Evaluation
>> Audrey >> >> On 2/24/20, 2:27 AM, "Paras Lehana" wrote: >> >>Hi Audrey, >> >>I work for Auto-Suggest at IndiaMART. Although we don't use the >> Suggester >>component, I think you need evaluation metrics for Auto-Suggest as a >>business product and not specifically for Solr Suggester which is the >>backend. We use edismax parser with EdgeNGrams Tokenization. >> >>Every week, as the property owner, I report around 500 metrics. I would >>like to mention a few of those: >> >> 1. MRR (Mean Reciprocal Rate): How high the user selection was >> among the >> returned result. Ranges from 0 to 1, the higher the better. >> 2. APL (Average Prefix Length): Prefix is the query by user. Lesser >> the >> better. This reports how less an average user has to type for >> getting the >> intended suggestion. >> 3. Acceptance Rate or Selection: How many of the total searches are >> being served from Auto-Suggest. We are around 50%. >> 4. Selection to Display Ratio: Did you make the user to click any >> of the >> suggestions if they are displayed? >> 5. Response Time: How fast are you serving your average query. >> >> >>The Selection and Response Time are our main KPIs. We track a lot about >>Auto-Suggest usage on our platform which becomes apparent if you >> observe >>the URL after clicking a suggestion on dir.indiamart.com. However, not >>everything would benefit you. Do let me know for any related query or >>explanation. Hope this helps. :) >> >>On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - >> audrey.lorberf...@ibm.com >> wrote: >> >>> Hi all, >>> >>> How do you all evaluate the success of your query autocomplete (i.e. >>> suggester) component if you use it? >>> >>> We cannot use MRR for various reasons (I can go into them if you're >>> interested), so we're thinking of using nDCG since we already use >> that for >>> relevance eval of our system as a whole. I am also interested in the >> metric >>> "success at top-k," but I can't find any research papers that >> explicitly >>> define "success" -- I am assuming it's a suggestion (or suggestions) >>> labeled "relevant," but maybe it could also simply be the suggestion >> that >>> receives a click from the user? >>> >>> Would love to hear from the hive mind! >>> >>> Best, >>> Audrey >>> >>> -- >>> >>> >>> >> >>-- >>-- >>Regards, >> >>*Paras Lehana* [65871] >>Development Engineer, *Auto-Suggest*, >>IndiaMART InterMESH Ltd, >> >>11th Floor, Tower 2, Assotech Business Cresterra, >>Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 >> >>Mob.: +91-9560911996 >>Work: 0120-4056700 | Extn: >>*11096* >> >>-- >>* >>* >> >> < >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=CTfu2EkiAFh-Ra4cn3EL2GdkKLBhD754dBAoRYpr2uc=kwWlK4TbSM6iPH6DBIrwg3QCeHrY-83N5hm2HtQQsjc= >>> >> >> >> > > -- > -- > Regards, > > *Paras Lehana* [65871] > Development Engineer, *Auto-Suggest*, > IndiaMART InterMESH Ltd, > > 11th Floor, Tower 2, Assotech Business Cresterra, > Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 > > Mob.: +91-9560911996 > Work: 0120-4056700 | Extn: > *11096* > > -- > * > * > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=e9a1kzjKu6l-P1g5agvpe-jQZfCF6bT4x6CeYDrUkgE=uqfrTqQq6XBBa280nv82Eg7m2eGlEQZ7PaCrN5CgDkg= >
Re: Re: Query Autocomplete Evaluation
eports how less an average user has to type for >> getting the >> intended suggestion. >> 3. Acceptance Rate or Selection: How many of the total searches are >> being served from Auto-Suggest. We are around 50%. >> 4. Selection to Display Ratio: Did you make the user to click any >> of the >> suggestions if they are displayed? >> 5. Response Time: How fast are you serving your average query. >> >> >>The Selection and Response Time are our main KPIs. We track a lot about >>Auto-Suggest usage on our platform which becomes apparent if you >> observe >>the URL after clicking a suggestion on dir.indiamart.com. However, not >>everything would benefit you. Do let me know for any related query or >>explanation. Hope this helps. :) >> >>On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - >> audrey.lorberf...@ibm.com >> wrote: >> >>> Hi all, >>> >>> How do you all evaluate the success of your query autocomplete (i.e. >>> suggester) component if you use it? >>> >>> We cannot use MRR for various reasons (I can go into them if you're >>> interested), so we're thinking of using nDCG since we already use >> that for >>> relevance eval of our system as a whole. I am also interested in the >> metric >>> "success at top-k," but I can't find any research papers that >> explicitly >>> define "success" -- I am assuming it's a suggestion (or suggestions) >>> labeled "relevant," but maybe it could also simply be the suggestion >> that >>> receives a click from the user? >>> >>> Would love to hear from the hive mind! >>> >>> Best, >>> Audrey >>> >>> -- >>> >>> >>> >> >>-- >>-- >>Regards, >> >>*Paras Lehana* [65871] >>Development Engineer, *Auto-Suggest*, >>IndiaMART InterMESH Ltd, >> >>11th Floor, Tower 2, Assotech Business Cresterra, >>Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 >> >>Mob.: +91-9560911996 >>Work: 0120-4056700 | Extn: >>*11096* >> >>-- >>* >>* >> >> < >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=CTfu2EkiAFh-Ra4cn3EL2GdkKLBhD754dBAoRYpr2uc=kwWlK4TbSM6iPH6DBIrwg3QCeHrY-83N5hm2HtQQsjc= >>> >> >> >> > > -- > -- > Regards, > > *Paras Lehana* [65871] > Development Engineer, *Auto-Suggest*, > IndiaMART InterMESH Ltd, > > 11th Floor, Tower 2, Assotech Business Cresterra, > Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 > > Mob.: +91-9560911996 > Work: 0120-4056700 | Extn: > *11096* > > -- > * > * > > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=e9a1kzjKu6l-P1g5agvpe-jQZfCF6bT4x6CeYDrUkgE=uqfrTqQq6XBBa280nv82Eg7m2eGlEQZ7PaCrN5CgDkg= >
Re: Query Autocomplete Evaluation
Here is a blog article with a worked example for MRR based on customer clicks. https://observer.wunderwood.org/2016/09/12/measuring-search-relevance-with-mrr/ At my place of work, we compare the CTR and MRR of queries using suggestions to those that do not use suggestions. Solr autosuggest based on lexicon of book titles is highly effective for us. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Feb 24, 2020, at 9:52 PM, Paras Lehana wrote: > > Hey Audrey, > > I assume MRR is about the ranking of the intended suggestion. For this, no > human judgement is required. We track position selection - the position > (1-10) of the selected suggestion. For example, this is our recent numbers: > > Position 1 Selected (B3) 107,699 > Position 2 Selected (B4) 58,736 > Position 3 Selected (B5) 23,507 > Position 4 Selected (B6) 12,250 > Position 5 Selected (B7) 7,980 > Position 6 Selected (B8) 5,653 > Position 7 Selected (B9) 4,193 > Position 8 Selected (B10) 3,511 > Position 9 Selected (B11) 2,997 > Position 10 Selected (B12) 2,428 > *Total Selections (B13)* *228,954* > MRR = (B3+B4/2+B5/3+B6/4+B7/5+B8/6+B9/7+B10/8+B11/9+B12/10)/B13 = 66.45% > > Refer here for MRR calculation keeping Auto-Suggest in perspective: > https://medium.com/@dtunkelang/evaluating-search-measuring-searcher-behavior-5f8347619eb0 > > "In practice, this is inverted to obtain the reciprocal rank, e.g., if the > searcher clicks on the 4th result, the reciprocal rank is 0.25. The average > of these reciprocal ranks is called the mean reciprocal rank (MRR)." > > nDCG may require human intervention. Please let me know in case I have not > understood your question properly. :) > > > > On Mon, 24 Feb 2020 at 20:49, Audrey Lorberfeld - audrey.lorberf...@ibm.com > wrote: > >> Hi Paras, >> >> This is SO helpful, thank you. Quick question about your MRR metric -- do >> you have binary human judgements for your suggestions? If no, how do you >> label suggestions successful or not? >> >> Best, >> Audrey >> >> On 2/24/20, 2:27 AM, "Paras Lehana" wrote: >> >>Hi Audrey, >> >>I work for Auto-Suggest at IndiaMART. Although we don't use the >> Suggester >>component, I think you need evaluation metrics for Auto-Suggest as a >>business product and not specifically for Solr Suggester which is the >>backend. We use edismax parser with EdgeNGrams Tokenization. >> >>Every week, as the property owner, I report around 500 metrics. I would >>like to mention a few of those: >> >> 1. MRR (Mean Reciprocal Rate): How high the user selection was >> among the >> returned result. Ranges from 0 to 1, the higher the better. >> 2. APL (Average Prefix Length): Prefix is the query by user. Lesser >> the >> better. This reports how less an average user has to type for >> getting the >> intended suggestion. >> 3. Acceptance Rate or Selection: How many of the total searches are >> being served from Auto-Suggest. We are around 50%. >> 4. Selection to Display Ratio: Did you make the user to click any >> of the >> suggestions if they are displayed? >> 5. Response Time: How fast are you serving your average query. >> >> >>The Selection and Response Time are our main KPIs. We track a lot about >>Auto-Suggest usage on our platform which becomes apparent if you >> observe >>the URL after clicking a suggestion on dir.indiamart.com. However, not >>everything would benefit you. Do let me know for any related query or >>explanation. Hope this helps. :) >> >>On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - >> audrey.lorberf...@ibm.com >> wrote: >> >>> Hi all, >>> >>> How do you all evaluate the success of your query autocomplete (i.e. >>> suggester) component if you use it? >>> >>> We cannot use MRR for various reasons (I can go into them if you're >>> interested), so we're thinking of using nDCG since we already use >> that for >>> relevance eval of our system as a whole. I am also interested in the >> metric >>> "success at top-k," but I can't find any research papers that >> explicitly >>> define "success" -- I am assuming it's a suggestion (or suggestions) >>> labeled "relevant," but maybe it could also simply be the suggestion >> that >>> receives a click from the user? >>> >>> Would love to hea
Re: Re: Query Autocomplete Evaluation
Hey Audrey, I assume MRR is about the ranking of the intended suggestion. For this, no human judgement is required. We track position selection - the position (1-10) of the selected suggestion. For example, this is our recent numbers: Position 1 Selected (B3) 107,699 Position 2 Selected (B4) 58,736 Position 3 Selected (B5) 23,507 Position 4 Selected (B6) 12,250 Position 5 Selected (B7) 7,980 Position 6 Selected (B8) 5,653 Position 7 Selected (B9) 4,193 Position 8 Selected (B10) 3,511 Position 9 Selected (B11) 2,997 Position 10 Selected (B12) 2,428 *Total Selections (B13)* *228,954* MRR = (B3+B4/2+B5/3+B6/4+B7/5+B8/6+B9/7+B10/8+B11/9+B12/10)/B13 = 66.45% Refer here for MRR calculation keeping Auto-Suggest in perspective: https://medium.com/@dtunkelang/evaluating-search-measuring-searcher-behavior-5f8347619eb0 "In practice, this is inverted to obtain the reciprocal rank, e.g., if the searcher clicks on the 4th result, the reciprocal rank is 0.25. The average of these reciprocal ranks is called the mean reciprocal rank (MRR)." nDCG may require human intervention. Please let me know in case I have not understood your question properly. :) On Mon, 24 Feb 2020 at 20:49, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Hi Paras, > > This is SO helpful, thank you. Quick question about your MRR metric -- do > you have binary human judgements for your suggestions? If no, how do you > label suggestions successful or not? > > Best, > Audrey > > On 2/24/20, 2:27 AM, "Paras Lehana" wrote: > > Hi Audrey, > > I work for Auto-Suggest at IndiaMART. Although we don't use the > Suggester > component, I think you need evaluation metrics for Auto-Suggest as a > business product and not specifically for Solr Suggester which is the > backend. We use edismax parser with EdgeNGrams Tokenization. > > Every week, as the property owner, I report around 500 metrics. I would > like to mention a few of those: > >1. MRR (Mean Reciprocal Rate): How high the user selection was > among the >returned result. Ranges from 0 to 1, the higher the better. >2. APL (Average Prefix Length): Prefix is the query by user. Lesser > the >better. This reports how less an average user has to type for > getting the >intended suggestion. >3. Acceptance Rate or Selection: How many of the total searches are >being served from Auto-Suggest. We are around 50%. >4. Selection to Display Ratio: Did you make the user to click any > of the >suggestions if they are displayed? >5. Response Time: How fast are you serving your average query. > > > The Selection and Response Time are our main KPIs. We track a lot about > Auto-Suggest usage on our platform which becomes apparent if you > observe > the URL after clicking a suggestion on dir.indiamart.com. However, not > everything would benefit you. Do let me know for any related query or > explanation. Hope this helps. :) > > On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - > audrey.lorberf...@ibm.com > wrote: > > > Hi all, > > > > How do you all evaluate the success of your query autocomplete (i.e. > > suggester) component if you use it? > > > > We cannot use MRR for various reasons (I can go into them if you're > > interested), so we're thinking of using nDCG since we already use > that for > > relevance eval of our system as a whole. I am also interested in the > metric > > "success at top-k," but I can't find any research papers that > explicitly > > define "success" -- I am assuming it's a suggestion (or suggestions) > > labeled "relevant," but maybe it could also simply be the suggestion > that > > receives a click from the user? > > > > Would love to hear from the hive mind! > > > > Best, > > Audrey > > > > -- > > > > > > > > -- > -- > Regards, > > *Paras Lehana* [65871] > Development Engineer, *Auto-Suggest*, > IndiaMART InterMESH Ltd, > > 11th Floor, Tower 2, Assotech Business Cresterra, > Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 > > Mob.: +91-9560911996 > Work: 0120-4056700 | Extn: > *11096* > > -- > * > * > > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=CTfu2EkiAFh-Ra4cn3EL2GdkKLBhD754dBAoRYpr2uc=kwWlK4TbSM6iPH6DBIrwg3QCeHrY-83N5hm2HtQQsjc= > > > > > -- -- Regards, *Paras Lehana* [65871] Development Engineer, *Auto-Suggest*, IndiaMART InterMESH Ltd, 11th Floor, Tower 2, Assotech Business Cresterra, Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 Mob.: +91-9560911996 Work: 0120-4056700 | Extn: *11096* -- * * <https://www.facebook.com/IndiaMART/videos/578196442936091/>
Re: Re: Query Autocomplete Evaluation
Hi Paras, This is SO helpful, thank you. Quick question about your MRR metric -- do you have binary human judgements for your suggestions? If no, how do you label suggestions successful or not? Best, Audrey On 2/24/20, 2:27 AM, "Paras Lehana" wrote: Hi Audrey, I work for Auto-Suggest at IndiaMART. Although we don't use the Suggester component, I think you need evaluation metrics for Auto-Suggest as a business product and not specifically for Solr Suggester which is the backend. We use edismax parser with EdgeNGrams Tokenization. Every week, as the property owner, I report around 500 metrics. I would like to mention a few of those: 1. MRR (Mean Reciprocal Rate): How high the user selection was among the returned result. Ranges from 0 to 1, the higher the better. 2. APL (Average Prefix Length): Prefix is the query by user. Lesser the better. This reports how less an average user has to type for getting the intended suggestion. 3. Acceptance Rate or Selection: How many of the total searches are being served from Auto-Suggest. We are around 50%. 4. Selection to Display Ratio: Did you make the user to click any of the suggestions if they are displayed? 5. Response Time: How fast are you serving your average query. The Selection and Response Time are our main KPIs. We track a lot about Auto-Suggest usage on our platform which becomes apparent if you observe the URL after clicking a suggestion on dir.indiamart.com. However, not everything would benefit you. Do let me know for any related query or explanation. Hope this helps. :) On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Hi all, > > How do you all evaluate the success of your query autocomplete (i.e. > suggester) component if you use it? > > We cannot use MRR for various reasons (I can go into them if you're > interested), so we're thinking of using nDCG since we already use that for > relevance eval of our system as a whole. I am also interested in the metric > "success at top-k," but I can't find any research papers that explicitly > define "success" -- I am assuming it's a suggestion (or suggestions) > labeled "relevant," but maybe it could also simply be the suggestion that > receives a click from the user? > > Would love to hear from the hive mind! > > Best, > Audrey > > -- > > > -- -- Regards, *Paras Lehana* [65871] Development Engineer, *Auto-Suggest*, IndiaMART InterMESH Ltd, 11th Floor, Tower 2, Assotech Business Cresterra, Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 Mob.: +91-9560911996 Work: 0120-4056700 | Extn: *11096* -- * * <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_IndiaMART_videos_578196442936091_=DwIBaQ=jf_iaSHvJObTbx-siA1ZOg=_8ViuZIeSRdQjONA8yHWPZIBlhj291HU3JpNIx5a55M=CTfu2EkiAFh-Ra4cn3EL2GdkKLBhD754dBAoRYpr2uc=kwWlK4TbSM6iPH6DBIrwg3QCeHrY-83N5hm2HtQQsjc= >
Re: Query Autocomplete Evaluation
Hi Audrey, I work for Auto-Suggest at IndiaMART. Although we don't use the Suggester component, I think you need evaluation metrics for Auto-Suggest as a business product and not specifically for Solr Suggester which is the backend. We use edismax parser with EdgeNGrams Tokenization. Every week, as the property owner, I report around 500 metrics. I would like to mention a few of those: 1. MRR (Mean Reciprocal Rate): How high the user selection was among the returned result. Ranges from 0 to 1, the higher the better. 2. APL (Average Prefix Length): Prefix is the query by user. Lesser the better. This reports how less an average user has to type for getting the intended suggestion. 3. Acceptance Rate or Selection: How many of the total searches are being served from Auto-Suggest. We are around 50%. 4. Selection to Display Ratio: Did you make the user to click any of the suggestions if they are displayed? 5. Response Time: How fast are you serving your average query. The Selection and Response Time are our main KPIs. We track a lot about Auto-Suggest usage on our platform which becomes apparent if you observe the URL after clicking a suggestion on dir.indiamart.com. However, not everything would benefit you. Do let me know for any related query or explanation. Hope this helps. :) On Fri, 14 Feb 2020 at 21:23, Audrey Lorberfeld - audrey.lorberf...@ibm.com wrote: > Hi all, > > How do you all evaluate the success of your query autocomplete (i.e. > suggester) component if you use it? > > We cannot use MRR for various reasons (I can go into them if you're > interested), so we're thinking of using nDCG since we already use that for > relevance eval of our system as a whole. I am also interested in the metric > "success at top-k," but I can't find any research papers that explicitly > define "success" -- I am assuming it's a suggestion (or suggestions) > labeled "relevant," but maybe it could also simply be the suggestion that > receives a click from the user? > > Would love to hear from the hive mind! > > Best, > Audrey > > -- > > > -- -- Regards, *Paras Lehana* [65871] Development Engineer, *Auto-Suggest*, IndiaMART InterMESH Ltd, 11th Floor, Tower 2, Assotech Business Cresterra, Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 201305 Mob.: +91-9560911996 Work: 0120-4056700 | Extn: *11096* -- * * <https://www.facebook.com/IndiaMART/videos/578196442936091/>
Query Autocomplete Evaluation
Hi all, How do you all evaluate the success of your query autocomplete (i.e. suggester) component if you use it? We cannot use MRR for various reasons (I can go into them if you're interested), so we're thinking of using nDCG since we already use that for relevance eval of our system as a whole. I am also interested in the metric "success at top-k," but I can't find any research papers that explicitly define "success" -- I am assuming it's a suggestion (or suggestions) labeled "relevant," but maybe it could also simply be the suggestion that receives a click from the user? Would love to hear from the hive mind! Best, Audrey --
Autocomplete results from multiple fields
Hi I am trying to implement autocomplete feature from two fields, name & attribute1. I have setup ngram for both the fields and have copyfield that stores the ngrams results. fl only contains name which is used by ui. Is it possible to display records that match on values from attribute1? The only way I can think of doing so is adding another document with type attribute ? Are there any other options that I can use? Thanks Jay
Re: Suggester autocomplete for address information
I'd like to clarify that what I am looking for is the right field type for
the address field that will suggest values as follows for the input:
Input:
"123 SM"
Suggestions:
- 123-127 SMITH STREET, KEMPSEY NSW 2440
- 123 SMYTHE STREET. RANDOM PLACE
And in addition to this I want the search to also provide results if I
simply include the postcode (4 integers here in Oz) as follows:
Input:
"2440"
Suggestions:
- 123-127 SMITH STREET, KEMPSEY NSW 2440
- 120 SMITH STREET, KEMPSEY NSW 2440
- 65 SMITH STREET, KEMPSEY NSW 2440
- 2440 ANOTHER RANDOM ROAD, RANDOM PLACE
In short I would like it to try to match the beginning part of the address
first and if that fails start using later parts of the string such as
suburb, state and postcode.
The field type that I'm currently using as the basis of these suggestions
is as follows:
<
filter class="solr.StopFilterFactory" words="lang/stopwords_en.txt"
ignoreCase="true"/>
Thanks,
Kehan
On Tue, 26 Feb 2019 at 21:54, Kehan Harman <
kehan.har...@gaiaresources.com.au> wrote:
> Hi All,
>
> I'm new to Solr & the community so feel free to ignore / remove if this is
> the incorrect mailing list for this query.
>
> I'm trying to build an autocomplete using a Solr index for addresses in a
> format similar to:
>
> 123 Smith Street, KEMPSEY, NSW 2440
>
> I'm looking to have these addresses suggest values to users based on their
> input with some spellchecking capability.
>
> My documents contain contents like:
> { "id":"ANSW718363409", "table":"ADDRESS_DEFAULT_GEOCODE", "address":"123-127
> SMITH STREET, KEMPSEY NSW 2440", "address_location":
> "-31.07321967,152.84505473", "address_latitude":-31.07322, "
> address_longitude":152.84506, "locality_pid":"NSW2119", "locality_latitude
> ":-31.060476, "locality_longitude":152.84819, "suburb_postcode":"KEMPSEY
> NSW 2440", "number_first":123, "number_last":127, "street_number":
> "123-127", "street_name":"SMITH", "street_type_code":"STREET", "
> locality_name":"KEMPSEY", "state_name":"NEW SOUTH WALES", "
> state_abbreviation":"NSW", "postcode":"2440", "_version_":
> 1626515771141128204}
>
> These are Australian addresses extracted from
> https://data.gov.au/dataset/ds-dga-19432f89-dc3a-4ef3-b943-5326ef1dbecc/details
> .
>
> My managed schema has the following fields - I'm using the example managed
> schema *sample_techproducts_configs* with some additional fields that
> have been added using the schema API.:
>
> stored="true"/> "false" indexed="true" stored="true"/> ="location" multiValued="false" indexed="true" stored="true"/> ="address_longitude" type="float" multiValued="false" indexed="true"
> stored="true"/> "false" indexed="true" stored="true"/> "string" multiValued="false" indexed="true" stored="true"/> "flat_number" type="int" multiValued="false" indexed="true" stored="true"
> /> "true" stored="true"/> stored="true"/> ="true" required="true" stored="true"/> "strings"/> indexed="true" stored="true"/> "float" multiValued="false" indexed="true" stored="true"/> "locality_location" type="location" multiValued="false" indexed="true"
> stored="true"/> "false" indexed="true" stored="true"/> "string" multiValued="false" indexed="true" stored="true"/> "locality_pid" type="string" multiValued="false" indexed="true" stored=
> "true"/> ="true" stored="true"/> multiValued="false" indexed="true" stored="true"/> "number_last" type="int" multiValued="false" indexed="true" stored="true"
> /> indexed="true" stored="true"/> multiValued="false" indexed="true" stored="true"/> "state_abbreviation" type="string" multiValued="false" indexed="true"
> stored="true"/> indexed=&qu
Suggester autocomplete for address information
Hi All,
I'm new to Solr & the community so feel free to ignore / remove if this is
the incorrect mailing list for this query.
I'm trying to build an autocomplete using a Solr index for addresses in a
format similar to:
123 Smith Street, KEMPSEY, NSW 2440
I'm looking to have these addresses suggest values to users based on their
input with some spellchecking capability.
My documents contain contents like:
{ "id":"ANSW718363409", "table":"ADDRESS_DEFAULT_GEOCODE", "address":"123-127
SMITH STREET, KEMPSEY NSW 2440", "address_location":
"-31.07321967,152.84505473", "address_latitude":-31.07322, "
address_longitude":152.84506, "locality_pid":"NSW2119", "locality_latitude":
-31.060476, "locality_longitude":152.84819, "suburb_postcode":"KEMPSEY NSW
2440", "number_first":123, "number_last":127, "street_number":"123-127", "
street_name":"SMITH", "street_type_code":"STREET", "locality_name":"KEMPSEY",
"state_name":"NEW SOUTH WALES", "state_abbreviation":"NSW", "postcode":
"2440", "_version_":1626515771141128204}
These are Australian addresses extracted from
https://data.gov.au/dataset/ds-dga-19432f89-dc3a-4ef3-b943-5326ef1dbecc/details
.
My managed schema has the following fields - I'm using the example managed
schema *sample_techproducts_configs* with some additional fields that have
been added using the schema API.:
<
field name="id" type="string" multiValued="false" indexed="true" required=
"true" stored="true"/>
The search component / requestHandler are defined as follows.
suburb
FuzzyLookupFactory
DocumentDictionaryFactory suburb_postcode string true
address FuzzyLookupFactory
DocumentDictionaryFactory address string true true 10 suggest
Please let me know if you need any more information in order to answer this?
Thanks,
Kehan
Re: Achieving AutoComplete feature using Solrj client
Indeed, you first configure it in the solrconfig.xml ( manually). Then you can query and parse the response as you like with the SolrJ client library. Cheers - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Achieving AutoComplete feature using Solrj client
Hi, Thank you for your help. As far as I understood, I cannot configure and enable the suggester through solrj client. The configuration should be done manually. Arunan On 18 June 2018 at 14:50, Alessandro Benedetti wrote: > Hi, > me and Tommaso contributed this few years ago.[1] > You can easily get the suggester response now from the Solr response. > Of course you need to configure and enable the suggester first.[2][3][4] > > > [1] https://issues.apache.org/jira/browse/SOLR-7719 > [2] https://sease.io/2015/07/solr-you-complete-me.html > [3] https://lucidworks.com/2015/03/04/solr-suggester/ > [4] > https://sease.io/2018/06/apache-lucene-blendedinfixsuggester-how-it- > works-bugs-and-improvements.html > > > > - > --- > Alessandro Benedetti > Search Consultant, R Software Engineer, Director > Sease Ltd. - www.sease.io > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >
Re: Achieving AutoComplete feature using Solrj client
Hi, me and Tommaso contributed this few years ago.[1] You can easily get the suggester response now from the Solr response. Of course you need to configure and enable the suggester first.[2][3][4] [1] https://issues.apache.org/jira/browse/SOLR-7719 [2] https://sease.io/2015/07/solr-you-complete-me.html [3] https://lucidworks.com/2015/03/04/solr-suggester/ [4] https://sease.io/2018/06/apache-lucene-blendedinfixsuggester-how-it-works-bugs-and-improvements.html - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Achieving AutoComplete feature using Solrj client
Hi, I am trying to upgrade a system which had an older version of Lucene library. I want to implement AutoCompletion feature using solrj client. In the earlier version they have used IndexSearcher class of lucene to do that. Is there any similar way to achieve it using solrj? I basically want to type a field's name and it should give me suggestions as a dropdown in my webpage. Thanks in Advance. Arunan
Re: Autocomplete returning shingles
Yes, faceting will work, you can use an old approach used for autocompletion[1] . Be sure you add the shingle filter to the appropriate index time analysis for the field you want. Facet values are extracted from the indexed terms, so calculating faceting and filtering by prefix should do the trick. [1] https://solr.pl/en/2013/03/25/autocomplete-on-multivalued-fields-using-faceting/ - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Autocomplete returning shingles
Yes, splitting in more documents would probably work. Don't think I can do this easliy with Solr. Looking into using facets now. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Autocomplete returning shingles
So, your problem is you want to return shingle suggestions from a field in input but apply multiple filter queries to the documents you want to fetch suggestions from. Are you building an auxiliary index for that ? You need to design it accordingly. If you want to to map each suggestion to a single document in the auxiliary index, when you build this auxiliary index you need to calculate the shingles client side and push the multiple documents ( suggestion) per original field content. To do that automatically in Solr I was thinking you could write an UpdateRequestProcessor that given in input the document, split it in multiple docs, but unfortunately the current architecture of UpdateRequestProcessors takes in input 1 Doc and and returns in output just 1 doc. So it is not a viable approach. Unfortunately the shingle filter here doesn't help, as the user want shingle in output ( analysers doesn't affect stored content) Cheers - --- Alessandro Benedetti Search Consultant, R Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: Autocomplete returning shingles
Can you just add the SingleFilter to your field? https://lucene.apache.org/solr/guide/6_6/filter-descriptions.html#FilterDescriptions-ShingleFilter On Wed, May 2, 2018 at 2:04 PM, O. Klein <kl...@octoweb.nl> wrote: > I need to use autocomplete with edismax (ngrams,edgegrams) to return > shingled > suggestions. Field value "new york city" needs to return on query "ne" -> > "new","new york","new york city". With suggester this is easy. But im > forced > to use edismax because I need to apply mutliple filter queries. > > What is best approach to deal with this? > > Any suggestions are appreciated. > > > > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >
Autocomplete returning shingles
I need to use autocomplete with edismax (ngrams,edgegrams) to return shingled suggestions. Field value "new york city" needs to return on query "ne" -> "new","new york","new york city". With suggester this is easy. But im forced to use edismax because I need to apply mutliple filter queries. What is best approach to deal with this? Any suggestions are appreciated. -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Re: unordered autocomplete search
Hi Mikhail, Thank you so much for your inpu. I am looking into this and let you know when I've tried this. @Walter: indeed, it should be included :). If my code works, I'll post it here. Many thanks, Niraj On Mon, Sep 4, 2017 at 5:27 PM, Walter Underwood <wun...@wunderwood.org> wrote: > This should probably be a feature of the analyzing infix suggester. > > Right now, the fuzzy suggester is broken with the file dictionary, so we > can’t use fuzzy suggestions at all. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > > > > On Sep 4, 2017, at 4:50 AM, Mikhail Khludnev <m...@apache.org> wrote: > > > > You probably can override AnalyzingInfixSuggester.finishQuery(Builder, > > boolean) where you can rip clauses from builder and change TermQueries/ > > PrefixQuery to FuzzyQueries. Let me know how it works, please. > > > > On Mon, Sep 4, 2017 at 2:27 PM, Niraj Aswani <nirajasw...@gmail.com> > wrote: > > > >> Hi Mikhali, > >> > >> Thank you very much for your quick response. > >> > >> This does seem to fix the issue of unordered words in the autocomplete, > >> however, then I loose the capability of matching misspelled words. > >> > >> Is there anything that can be done to combine the functionality of the > two? > >> > >> Regards, > >> Niraj > >> > >> > >> > >> On Mon, Sep 4, 2017 at 11:13 AM, Mikhail Khludnev <m...@apache.org> > wrote: > >> > >>> The first question is, "sourceLocation">test.dict makes sense? > >>> Then, for me, it looks like a case for AnalyzingInfixLookupFactory > >>> https://lucidworks.com/2015/03/04/solr-suggester/ rather than > >>> > >>> - The FuzzyLookupFactory that creates suggestions for misspelled > words > >>> in fields. > >>> > >>> > >>> > >>> > >>> On Mon, Sep 4, 2017 at 11:57 AM, Niraj Aswani <nirajasw...@gmail.com> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> I am using solr 5.5.4. > >>>> > >>>> I would like to perform an unordered autocomplete search however it > >> seems > >>>> that it only suggests phrases that start with my term in the query. > >>>> > >>>> For example, in my dictionary I have, > >>>> > >>>> *lamp desk* > >>>> > >>>> When searching for the term "lamp", it is able to show the the > >> suggestion > >>>> "lamp desk" as the suggestion is starting with the word "lamp". > >> However, > >>>> when I search for the term "desk", it doesn't show any suggestion. > >>>> > >>>> My field in the *managed-schema* is as below: > >>>> > >>>> >>>> positionIncrementGap="100"> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> My controller in *solconfig.xml* is defined as the following: > >>>> > >>>> > >>>> > >>>> > >>>>default > >>>>FuzzyLookupFactory > >>>>test.dict > >>>>suggest_field > >>>> > >>>> > >>>> > >>>> >>> startup="lazy"> > >>>> > >>>>true > >>>>10 > >>>> > >>>> > >>>>suggest > >>>> > >>>> > >>>> > >>>> The *query* I fire is: > >>>> > >>>> http://localhost:8983/solr/core1/suggest?q=desk=true > >>>> > >>>> is there anyway, I can get the above scenario working? > >>>> > >>>> Many thanks, > >>>> Niraj > >>>> > >>> > >>> > >>> > >>> -- > >>> Sincerely yours > >>> Mikhail Khludnev > >>> > >> > > > > > > > > -- > > Sincerely yours > > Mikhail Khludnev > >
Re: unordered autocomplete search
This should probably be a feature of the analyzing infix suggester. Right now, the fuzzy suggester is broken with the file dictionary, so we can’t use fuzzy suggestions at all. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Sep 4, 2017, at 4:50 AM, Mikhail Khludnev <m...@apache.org> wrote: > > You probably can override AnalyzingInfixSuggester.finishQuery(Builder, > boolean) where you can rip clauses from builder and change TermQueries/ > PrefixQuery to FuzzyQueries. Let me know how it works, please. > > On Mon, Sep 4, 2017 at 2:27 PM, Niraj Aswani <nirajasw...@gmail.com> wrote: > >> Hi Mikhali, >> >> Thank you very much for your quick response. >> >> This does seem to fix the issue of unordered words in the autocomplete, >> however, then I loose the capability of matching misspelled words. >> >> Is there anything that can be done to combine the functionality of the two? >> >> Regards, >> Niraj >> >> >> >> On Mon, Sep 4, 2017 at 11:13 AM, Mikhail Khludnev <m...@apache.org> wrote: >> >>> The first question is, "sourceLocation">test.dict makes sense? >>> Then, for me, it looks like a case for AnalyzingInfixLookupFactory >>> https://lucidworks.com/2015/03/04/solr-suggester/ rather than >>> >>> - The FuzzyLookupFactory that creates suggestions for misspelled words >>> in fields. >>> >>> >>> >>> >>> On Mon, Sep 4, 2017 at 11:57 AM, Niraj Aswani <nirajasw...@gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> I am using solr 5.5.4. >>>> >>>> I would like to perform an unordered autocomplete search however it >> seems >>>> that it only suggests phrases that start with my term in the query. >>>> >>>> For example, in my dictionary I have, >>>> >>>> *lamp desk* >>>> >>>> When searching for the term "lamp", it is able to show the the >> suggestion >>>> "lamp desk" as the suggestion is starting with the word "lamp". >> However, >>>> when I search for the term "desk", it doesn't show any suggestion. >>>> >>>> My field in the *managed-schema* is as below: >>>> >>>> >>> positionIncrementGap="100"> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> My controller in *solconfig.xml* is defined as the following: >>>> >>>> >>>> >>>> >>>>default >>>>FuzzyLookupFactory >>>>test.dict >>>>suggest_field >>>> >>>> >>>> >>>> >> startup="lazy"> >>>> >>>>true >>>>10 >>>> >>>> >>>>suggest >>>> >>>> >>>> >>>> The *query* I fire is: >>>> >>>> http://localhost:8983/solr/core1/suggest?q=desk=true >>>> >>>> is there anyway, I can get the above scenario working? >>>> >>>> Many thanks, >>>> Niraj >>>> >>> >>> >>> >>> -- >>> Sincerely yours >>> Mikhail Khludnev >>> >> > > > > -- > Sincerely yours > Mikhail Khludnev
Re: unordered autocomplete search
You probably can override AnalyzingInfixSuggester.finishQuery(Builder, boolean) where you can rip clauses from builder and change TermQueries/ PrefixQuery to FuzzyQueries. Let me know how it works, please. On Mon, Sep 4, 2017 at 2:27 PM, Niraj Aswani <nirajasw...@gmail.com> wrote: > Hi Mikhali, > > Thank you very much for your quick response. > > This does seem to fix the issue of unordered words in the autocomplete, > however, then I loose the capability of matching misspelled words. > > Is there anything that can be done to combine the functionality of the two? > > Regards, > Niraj > > > > On Mon, Sep 4, 2017 at 11:13 AM, Mikhail Khludnev <m...@apache.org> wrote: > > > The first question is, "sourceLocation">test.dict makes sense? > > Then, for me, it looks like a case for AnalyzingInfixLookupFactory > > https://lucidworks.com/2015/03/04/solr-suggester/ rather than > > > >- The FuzzyLookupFactory that creates suggestions for misspelled words > >in fields. > > > > > > > > > > On Mon, Sep 4, 2017 at 11:57 AM, Niraj Aswani <nirajasw...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I am using solr 5.5.4. > > > > > > I would like to perform an unordered autocomplete search however it > seems > > > that it only suggests phrases that start with my term in the query. > > > > > > For example, in my dictionary I have, > > > > > > *lamp desk* > > > > > > When searching for the term "lamp", it is able to show the the > suggestion > > > "lamp desk" as the suggestion is starting with the word "lamp". > However, > > > when I search for the term "desk", it doesn't show any suggestion. > > > > > > My field in the *managed-schema* is as below: > > > > > > > > positionIncrementGap="100"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > My controller in *solconfig.xml* is defined as the following: > > > > > > > > > > > > > > > default > > > FuzzyLookupFactory > > > test.dict > > > suggest_field > > > > > > > > > > > > > startup="lazy"> > > > > > > true > > > 10 > > > > > > > > > suggest > > > > > > > > > > > > The *query* I fire is: > > > > > > http://localhost:8983/solr/core1/suggest?q=desk=true > > > > > > is there anyway, I can get the above scenario working? > > > > > > Many thanks, > > > Niraj > > > > > > > > > > > -- > > Sincerely yours > > Mikhail Khludnev > > > -- Sincerely yours Mikhail Khludnev
Re: unordered autocomplete search
Hi Mikhali, Thank you very much for your quick response. This does seem to fix the issue of unordered words in the autocomplete, however, then I loose the capability of matching misspelled words. Is there anything that can be done to combine the functionality of the two? Regards, Niraj On Mon, Sep 4, 2017 at 11:13 AM, Mikhail Khludnev <m...@apache.org> wrote: > The first question is, "sourceLocation">test.dict makes sense? > Then, for me, it looks like a case for AnalyzingInfixLookupFactory > https://lucidworks.com/2015/03/04/solr-suggester/ rather than > >- The FuzzyLookupFactory that creates suggestions for misspelled words >in fields. > > > > > On Mon, Sep 4, 2017 at 11:57 AM, Niraj Aswani <nirajasw...@gmail.com> > wrote: > > > Hi, > > > > I am using solr 5.5.4. > > > > I would like to perform an unordered autocomplete search however it seems > > that it only suggests phrases that start with my term in the query. > > > > For example, in my dictionary I have, > > > > *lamp desk* > > > > When searching for the term "lamp", it is able to show the the suggestion > > "lamp desk" as the suggestion is starting with the word "lamp". However, > > when I search for the term "desk", it doesn't show any suggestion. > > > > My field in the *managed-schema* is as below: > > > > > positionIncrementGap="100"> > > > > > > > > > > > > > > > > > > > > My controller in *solconfig.xml* is defined as the following: > > > > > > > > > > default > > FuzzyLookupFactory > > test.dict > > suggest_field > > > > > > > > startup="lazy"> > > > > true > > 10 > > > > > > suggest > > > > > > > > The *query* I fire is: > > > > http://localhost:8983/solr/core1/suggest?q=desk=true > > > > is there anyway, I can get the above scenario working? > > > > Many thanks, > > Niraj > > > > > > -- > Sincerely yours > Mikhail Khludnev >
Re: unordered autocomplete search
The first question is, "sourceLocation">test.dict makes sense? Then, for me, it looks like a case for AnalyzingInfixLookupFactory https://lucidworks.com/2015/03/04/solr-suggester/ rather than - The FuzzyLookupFactory that creates suggestions for misspelled words in fields. On Mon, Sep 4, 2017 at 11:57 AM, Niraj Aswani <nirajasw...@gmail.com> wrote: > Hi, > > I am using solr 5.5.4. > > I would like to perform an unordered autocomplete search however it seems > that it only suggests phrases that start with my term in the query. > > For example, in my dictionary I have, > > *lamp desk* > > When searching for the term "lamp", it is able to show the the suggestion > "lamp desk" as the suggestion is starting with the word "lamp". However, > when I search for the term "desk", it doesn't show any suggestion. > > My field in the *managed-schema* is as below: > > positionIncrementGap="100"> > > > > > > > > > > My controller in *solconfig.xml* is defined as the following: > > > > > default > FuzzyLookupFactory > test.dict > suggest_field > > > > > > true > 10 > > > suggest > > > > The *query* I fire is: > > http://localhost:8983/solr/core1/suggest?q=desk=true > > is there anyway, I can get the above scenario working? > > Many thanks, > Niraj > -- Sincerely yours Mikhail Khludnev
unordered autocomplete search
Hi, I am using solr 5.5.4. I would like to perform an unordered autocomplete search however it seems that it only suggests phrases that start with my term in the query. For example, in my dictionary I have, *lamp desk* When searching for the term "lamp", it is able to show the the suggestion "lamp desk" as the suggestion is starting with the word "lamp". However, when I search for the term "desk", it doesn't show any suggestion. My field in the *managed-schema* is as below: My controller in *solconfig.xml* is defined as the following: default FuzzyLookupFactory test.dict suggest_field true 10 suggest The *query* I fire is: http://localhost:8983/solr/core1/suggest?q=desk=true is there anyway, I can get the above scenario working? Many thanks, Niraj
Re: Use Solr Suggest to autocomplete words and suggest co-occurences
Hello, Georg!
Have you seen
http://blog.mikemccandless.com/2014/01/finding-long-tail-suggestions-using.html
?
On Sun, Mar 5, 2017 at 11:43 PM, Georg Sorst <georg.so...@gmail.com> wrote:
> Hi all,
>
> is there a way to get the suggester to autocomplete words and suggest
> co-occurences instead of suggesting complete field values? The behavior I'm
> looking for is quite similar to Google, only based on index values not
> actual queries.
>
> Let's say there are two items in the index:
>
>1. "Adidas running shoe"
>2. "Nike running shoe"
>
> Now when the user types in "running sh" the suggestions should be something
> like:
>
>- "running shoe" (completion)
>- "running shoe adidas" (completion + co-ocurrence)
>- "running shoe nike" (completion + co-ocurrence)
>
> I've actually got this running already through some abomination that abuses
> the facets built on the title field. This works surprisingly well, but I
> can't find a way to make this error-tolerant ("runing sh" with a single "n"
> should provide the same suggestions).
>
> So, any ideas on how to get the suggester do this in a error-tolerant way?
>
> Thanks and all the best,
> Georg
>
--
Sincerely yours
Mikhail Khludnev
Re: Use Solr Suggest to autocomplete words and suggest co-occurences
The significantTerms streaming expression could be useful as a
co-occurrence based suggester. This coming in Solr 6.5 but could be easily
backported to earlier releases. This blog describes how it works:
http://joelsolr.blogspot.com/2017/02/anomaly-detection-in-solr-65.html
Joel Bernstein
http://joelsolr.blogspot.com/
On Sun, Mar 5, 2017 at 3:43 PM, Georg Sorst <georg.so...@gmail.com> wrote:
> Hi all,
>
> is there a way to get the suggester to autocomplete words and suggest
> co-occurences instead of suggesting complete field values? The behavior I'm
> looking for is quite similar to Google, only based on index values not
> actual queries.
>
> Let's say there are two items in the index:
>
>1. "Adidas running shoe"
>2. "Nike running shoe"
>
> Now when the user types in "running sh" the suggestions should be something
> like:
>
>- "running shoe" (completion)
>- "running shoe adidas" (completion + co-ocurrence)
>- "running shoe nike" (completion + co-ocurrence)
>
> I've actually got this running already through some abomination that abuses
> the facets built on the title field. This works surprisingly well, but I
> can't find a way to make this error-tolerant ("runing sh" with a single "n"
> should provide the same suggestions).
>
> So, any ideas on how to get the suggester do this in a error-tolerant way?
>
> Thanks and all the best,
> Georg
>
Use Solr Suggest to autocomplete words and suggest co-occurences
Hi all,
is there a way to get the suggester to autocomplete words and suggest
co-occurences instead of suggesting complete field values? The behavior I'm
looking for is quite similar to Google, only based on index values not
actual queries.
Let's say there are two items in the index:
1. "Adidas running shoe"
2. "Nike running shoe"
Now when the user types in "running sh" the suggestions should be something
like:
- "running shoe" (completion)
- "running shoe adidas" (completion + co-ocurrence)
- "running shoe nike" (completion + co-ocurrence)
I've actually got this running already through some abomination that abuses
the facets built on the title field. This works surprisingly well, but I
can't find a way to make this error-tolerant ("runing sh" with a single "n"
should provide the same suggestions).
So, any ideas on how to get the suggester do this in a error-tolerant way?
Thanks and all the best,
Georg
Re: multiple but identical suggestions in autocomplete
Related this, I just created this : https://issues.apache.org/jira/browse/SOLR-8672 To be fair, I see no utility in returning duplicate suggestions ( if they have no different payload, they are un-distinguishable from a human perspective hence useless to have duplication) . I would like to hear some counter example. In my opinion we should contribute a way to avoid the duplicates directly in Solr. If there are valid counter examples, we could add an additional parameter for the solr.SuggestComponent like boolean . In a lot of scenarios I guess it could be a good fit. Cheers On 5 August 2015 at 12:06, Nutch Solr User <nutchsolru...@gmail.com> wrote: > You will need to call this service from UI as you are calling suggester > component currently. (may be on every key-press event in text box). You > will > pass required parameters too. > > Service will internally form a solr suggester query and query Solr. From > the > returned response it will keep only unique suggestions from top N > suggestions and return suggestions to UI. > > > > - > Nutch Solr User > > "The ultimate search engine would basically understand everything in the > world, and it would always give you the right thing." > -- > View this message in context: > http://lucene.472066.n3.nabble.com/multiple-but-identical-suggestions-in-autocomplete-tp4220055p4220953.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Autocomplete prototype using Velocity UI Browse - Solritas
Hi guys, I was playing with the velocity Browse UI, to provide a simple prototype to be shown to not techie users. Unfortunately I am a super noob in reading/writing front end and Js code. I would like an advice from you. What I would like to do is to bypass the big autocomplete script and simply automatically call the submit query on each key pressed. ( like google instant search) . it is something really only for a simple prototype, I don't care if it will be slow or not elegant. Anyone with some Js experience with the velocity template that can give me some quick hint to obtain that ? In the meantime I will continue investigating, but an help would be much appreciated. Cheers -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: Autocomplete prototype using Velocity UI Browse - Solritas
Ah… I did this once upon a time for techproducts, and put a branch of it here, see the couple of commits from me there: https://github.com/erikhatcher/lucene-solr/commits/instant_search <https://github.com/erikhatcher/lucene-solr/commits/instant_search> But, even better is to look at Solr’s example/files (see README on the quick start of that). It’s got instant search wired in to that. Index some docs / web crawl and see how it behaves for inspiration. — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com <http://www.lucidworks.com/> > On Oct 28, 2015, at 12:38 PM, Alessandro Benedetti <abenede...@apache.org> > wrote: > > I am using 5.3 . > I was taking a look to the vm templates and Js scripts. > > My collection is a custom collection, and it is working ok. > The browse interface is slightly customise and it is working properly. > > Everytime I click submit query , the proper results are returned. > > What i would like to do is slightly customise the vm or Js, to have the > submit sent automatically overtime I type something in the search box. > Something similar to google instant search. > It's for a prototype so it's not critical for performances or elegance . > is it clearer ? > > Cheers > > On 28 October 2015 at 16:13, Erik Hatcher <erik.hatc...@gmail.com > <mailto:erik.hatc...@gmail.com>> wrote: > >> What version of Solr? Solr 5’s data driven configuration is set up to >> use a generic browse interface that does not have any auto-suggest wired in >> by default. >> >> How did you create your collection? You just want to turn off the terms >> suggest thing? >> >> — >> Erik Hatcher, Senior Solutions Architect >> http://www.lucidworks.com <http://www.lucidworks.com/> >> <http://www.lucidworks.com/ <http://www.lucidworks.com/>> >> >> >> >> >>> On Oct 28, 2015, at 11:45 AM, Alessandro Benedetti < >> abenede...@apache.org> wrote: >>> >>> Hi guys, >>> I was playing with the velocity Browse UI, to provide a simple prototype >> to >>> be shown to not techie users. >>> >>> Unfortunately I am a super noob in reading/writing front end and Js code. >>> I would like an advice from you. >>> What I would like to do is to bypass the big autocomplete script and >> simply >>> automatically call the submit query on each key pressed. ( like google >>> instant search) . >>> >>> it is something really only for a simple prototype, I don't care if it >> will >>> be slow or not elegant. >>> Anyone with some Js experience with the velocity template that can give >> me >>> some quick hint to obtain that ? >>> In the meantime I will continue investigating, but an help would be much >>> appreciated. >>> >>> Cheers >>> >>> -- >>> -- >>> >>> Benedetti Alessandro >>> Visiting card : http://about.me/alessandro_benedetti >>> >>> "Tyger, tyger burning bright >>> In the forests of the night, >>> What immortal hand or eye >>> Could frame thy fearful symmetry?" >>> >>> William Blake - Songs of Experience -1794 England >> >> > > > -- > -- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > <http://about.me/alessandro_benedetti> > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England
Re: Autocomplete prototype using Velocity UI Browse - Solritas
I am using 5.3 . I was taking a look to the vm templates and Js scripts. My collection is a custom collection, and it is working ok. The browse interface is slightly customise and it is working properly. Everytime I click submit query , the proper results are returned. What i would like to do is slightly customise the vm or Js, to have the submit sent automatically overtime I type something in the search box. Something similar to google instant search. It's for a prototype so it's not critical for performances or elegance . is it clearer ? Cheers On 28 October 2015 at 16:13, Erik Hatcher <erik.hatc...@gmail.com> wrote: > What version of Solr? Solr 5’s data driven configuration is set up to > use a generic browse interface that does not have any auto-suggest wired in > by default. > > How did you create your collection? You just want to turn off the terms > suggest thing? > > — > Erik Hatcher, Senior Solutions Architect > http://www.lucidworks.com <http://www.lucidworks.com/> > > > > > > On Oct 28, 2015, at 11:45 AM, Alessandro Benedetti < > abenede...@apache.org> wrote: > > > > Hi guys, > > I was playing with the velocity Browse UI, to provide a simple prototype > to > > be shown to not techie users. > > > > Unfortunately I am a super noob in reading/writing front end and Js code. > > I would like an advice from you. > > What I would like to do is to bypass the big autocomplete script and > simply > > automatically call the submit query on each key pressed. ( like google > > instant search) . > > > > it is something really only for a simple prototype, I don't care if it > will > > be slow or not elegant. > > Anyone with some Js experience with the velocity template that can give > me > > some quick hint to obtain that ? > > In the meantime I will continue investigating, but an help would be much > > appreciated. > > > > Cheers > > > > -- > > -- > > > > Benedetti Alessandro > > Visiting card : http://about.me/alessandro_benedetti > > > > "Tyger, tyger burning bright > > In the forests of the night, > > What immortal hand or eye > > Could frame thy fearful symmetry?" > > > > William Blake - Songs of Experience -1794 England > > -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: Autocomplete prototype using Velocity UI Browse - Solritas
What version of Solr? Solr 5’s data driven configuration is set up to use a generic browse interface that does not have any auto-suggest wired in by default. How did you create your collection? You just want to turn off the terms suggest thing? — Erik Hatcher, Senior Solutions Architect http://www.lucidworks.com <http://www.lucidworks.com/> > On Oct 28, 2015, at 11:45 AM, Alessandro Benedetti <abenede...@apache.org> > wrote: > > Hi guys, > I was playing with the velocity Browse UI, to provide a simple prototype to > be shown to not techie users. > > Unfortunately I am a super noob in reading/writing front end and Js code. > I would like an advice from you. > What I would like to do is to bypass the big autocomplete script and simply > automatically call the submit query on each key pressed. ( like google > instant search) . > > it is something really only for a simple prototype, I don't care if it will > be slow or not elegant. > Anyone with some Js experience with the velocity template that can give me > some quick hint to obtain that ? > In the meantime I will continue investigating, but an help would be much > appreciated. > > Cheers > > -- > -- > > Benedetti Alessandro > Visiting card : http://about.me/alessandro_benedetti > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England
Re: Autocomplete prototype using Velocity UI Browse - Solritas
Erick, thank you very much ! Just used the example in files, and it's perfect for my need ! Cheers On 28 October 2015 at 16:43, Erik Hatcher <erik.hatc...@gmail.com> wrote: > Ah… I did this once upon a time for techproducts, and put a branch of it > here, see the couple of commits from me there: > > https://github.com/erikhatcher/lucene-solr/commits/instant_search < > https://github.com/erikhatcher/lucene-solr/commits/instant_search> > > But, even better is to look at Solr’s example/files (see README on the > quick start of that). It’s got instant search wired in to that. Index > some docs / web crawl and see how it behaves for inspiration. > > — > Erik Hatcher, Senior Solutions Architect > http://www.lucidworks.com <http://www.lucidworks.com/> > > > > > > On Oct 28, 2015, at 12:38 PM, Alessandro Benedetti < > abenede...@apache.org> wrote: > > > > I am using 5.3 . > > I was taking a look to the vm templates and Js scripts. > > > > My collection is a custom collection, and it is working ok. > > The browse interface is slightly customise and it is working properly. > > > > Everytime I click submit query , the proper results are returned. > > > > What i would like to do is slightly customise the vm or Js, to have the > > submit sent automatically overtime I type something in the search box. > > Something similar to google instant search. > > It's for a prototype so it's not critical for performances or elegance . > > is it clearer ? > > > > Cheers > > > > On 28 October 2015 at 16:13, Erik Hatcher <erik.hatc...@gmail.com > <mailto:erik.hatc...@gmail.com>> wrote: > > > >> What version of Solr? Solr 5’s data driven configuration is set up to > >> use a generic browse interface that does not have any auto-suggest > wired in > >> by default. > >> > >> How did you create your collection? You just want to turn off the terms > >> suggest thing? > >> > >> — > >> Erik Hatcher, Senior Solutions Architect > >> http://www.lucidworks.com <http://www.lucidworks.com/> < > http://www.lucidworks.com/ <http://www.lucidworks.com/>> > >> > >> > >> > >> > >>> On Oct 28, 2015, at 11:45 AM, Alessandro Benedetti < > >> abenede...@apache.org> wrote: > >>> > >>> Hi guys, > >>> I was playing with the velocity Browse UI, to provide a simple > prototype > >> to > >>> be shown to not techie users. > >>> > >>> Unfortunately I am a super noob in reading/writing front end and Js > code. > >>> I would like an advice from you. > >>> What I would like to do is to bypass the big autocomplete script and > >> simply > >>> automatically call the submit query on each key pressed. ( like google > >>> instant search) . > >>> > >>> it is something really only for a simple prototype, I don't care if it > >> will > >>> be slow or not elegant. > >>> Anyone with some Js experience with the velocity template that can give > >> me > >>> some quick hint to obtain that ? > >>> In the meantime I will continue investigating, but an help would be > much > >>> appreciated. > >>> > >>> Cheers > >>> > >>> -- > >>> -- > >>> > >>> Benedetti Alessandro > >>> Visiting card : http://about.me/alessandro_benedetti > >>> > >>> "Tyger, tyger burning bright > >>> In the forests of the night, > >>> What immortal hand or eye > >>> Could frame thy fearful symmetry?" > >>> > >>> William Blake - Songs of Experience -1794 England > >> > >> > > > > > > -- > > -- > > > > Benedetti Alessandro > > Visiting card : http://about.me/alessandro_benedetti < > http://about.me/alessandro_benedetti> > > > > "Tyger, tyger burning bright > > In the forests of the night, > > What immortal hand or eye > > Could frame thy fearful symmetry?" > > > > William Blake - Songs of Experience -1794 England > > -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: AutoComplete Feature in Solr
I would suggest you to read this in details : *DocumentDictionaryFactory* > A dictionary with terms, weights, and an optional payload taken from the > index. > This dictionary implementation takes the following parameters in addition > to parameters described for the Suggester generally and for the lookup > implementation: > >- weightField: A field that is stored or a numeric DocValue field. >This field is optional. > > >- payloadField: The payloadField should be a field that is stored. >This field is optional. > > >- contextField: Field to be used for context filtering. Note that only >some lookup implementations support filtering. > > DocumentExpressionDictionaryFactory > This dictionary implementation is the same as the > DocumentDictionaryFactory but allows users to specify an arbitrary > expression into the 'weightExpression' tag. > This dictionary implementation takes the following parameters in addition > to parameters described for the Suggester generally and for the lookup > implementation: > >- payloadField: The payloadField should be a field that is stored. >This field is optional. > > >- weightExpression: An arbitrary expression used for scoring the >suggestions. The fields used must be numeric fields. This field is > required. > > >- contextField: Field to be used for context filtering. Note that only >some lookup implementations support filtering. > > *HighFrequencyDictionaryFactory* > This dictionary implementation allows adding a threshold to prune out less > frequent terms in cases where very common terms may overwhelm other terms. > This dictionary implementation takes one parameter in addition to > parameters described for the Suggester generally and for the lookup > implementation: > >- threshold: A value between zero and one representing the minimum >fraction of the total documents where a term should appear in order to be >added to the lookup dictionary. > > Then play a little bit with the lookup implementation you want. Can be useful to play with those 2 attributes of the config : mySuggester ... price ... altSuggester ... ((price * 2) + ln(popularity)) weight price ... Hope this helps, Cheers On 14 October 2015 at 19:58, Salman Ansari <salman.rah...@gmail.com> wrote: > Actually what you mentioned Alessandro is something interesting for me. I > am looking to boost the ranking of some suggestions based on some dynamic > criteria (let's say how frequent they are used). Do I need to update the > boost field each time I request the suggestion (to capture the frequency)? > If you can direct me to an article that explains this with some scenarios > of using boost that would be appreciated. > > Regards, > Salman > > > On Wed, Oct 14, 2015 at 11:49 AM, Alessandro Benedetti < > benedetti.ale...@gmail.com> wrote: > > > using the suggester feature you can in some case rank the suggestions > based > > on an additional numeric field. > > It's not your use case, you actually want to use a search handler with a > > well defined schema that will allow you for example to query on an edge > > ngram token filtered field, applying a geo distance boost function. > > > > This is what i would use and would work fine with your applied filter > > queries as well ( reducing the space of Suggestions) > > > > Cheers > > > > On 14 October 2015 at 05:09, William Bell <billnb...@gmail.com> wrote: > > > > > We want to use suggester but also want to show those results closest to > > my > > > lat,long... Kinda combine suggester and bq=geodist() > > > > > > On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari < > salman.rah...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > I have been trying to get the autocomplete feature in Solr working > with > > > no > > > > luck up to now. First I read that "suggest component" is the > > recommended > > > > way as in the below article (and this is the exact functionality I am > > > > looking for, which is to autocomplete multiple words) > > > > > > > > > > > > > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > > > > > > > Then I tried implementing suggest as described in the following > > articles > > > in > > > > this order > > > > 1) > https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > > > > 2) http://solr.pl/en/2010/11/15/solr-a
Re: AutoComplete Feature in Solr
using the suggester feature you can in some case rank the suggestions based on an additional numeric field. It's not your use case, you actually want to use a search handler with a well defined schema that will allow you for example to query on an edge ngram token filtered field, applying a geo distance boost function. This is what i would use and would work fine with your applied filter queries as well ( reducing the space of Suggestions) Cheers On 14 October 2015 at 05:09, William Bell <billnb...@gmail.com> wrote: > We want to use suggester but also want to show those results closest to my > lat,long... Kinda combine suggester and bq=geodist() > > On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari <salman.rah...@gmail.com> > wrote: > > > Hi, > > > > I have been trying to get the autocomplete feature in Solr working with > no > > luck up to now. First I read that "suggest component" is the recommended > > way as in the below article (and this is the exact functionality I am > > looking for, which is to autocomplete multiple words) > > > > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > > > Then I tried implementing suggest as described in the following articles > in > > this order > > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > > implemented suggesting phrases) > > 3) > > > > > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > > > With no luck, after implementing each article when I run my query as > > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > > > > > I get > > > > > > 0 > > 0 > > > > > > > > Although I have an entry for Barack Obama in my index. I am posting my > > Solr configuration as well > > > > > > > > suggest > > org.apache.solr.spelling.suggest.Suggester > >> name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > > entity_autocomplete > > true > > > > > > > > > class="org.apache.solr.handler.component.SearchHandler"> > > > > true > > suggest > > 10 > > true > > false > > > > > > suggest > > > > > > > > It looks like a very simple job, but even after following so many > articles, > > I could not get it right. Any comment will be appreciated! > > > > Regards, > > Salman > > > > > > -- > Bill Bell > billnb...@gmail.com > cell 720-256-8076 > -- -- Benedetti Alessandro Visiting card - http://about.me/alessandro_benedetti Blog - http://alexbenedetti.blogspot.co.uk "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: AutoComplete Feature in Solr
Actually what you mentioned Alessandro is something interesting for me. I am looking to boost the ranking of some suggestions based on some dynamic criteria (let's say how frequent they are used). Do I need to update the boost field each time I request the suggestion (to capture the frequency)? If you can direct me to an article that explains this with some scenarios of using boost that would be appreciated. Regards, Salman On Wed, Oct 14, 2015 at 11:49 AM, Alessandro Benedetti < benedetti.ale...@gmail.com> wrote: > using the suggester feature you can in some case rank the suggestions based > on an additional numeric field. > It's not your use case, you actually want to use a search handler with a > well defined schema that will allow you for example to query on an edge > ngram token filtered field, applying a geo distance boost function. > > This is what i would use and would work fine with your applied filter > queries as well ( reducing the space of Suggestions) > > Cheers > > On 14 October 2015 at 05:09, William Bell <billnb...@gmail.com> wrote: > > > We want to use suggester but also want to show those results closest to > my > > lat,long... Kinda combine suggester and bq=geodist() > > > > On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari <salman.rah...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I have been trying to get the autocomplete feature in Solr working with > > no > > > luck up to now. First I read that "suggest component" is the > recommended > > > way as in the below article (and this is the exact functionality I am > > > looking for, which is to autocomplete multiple words) > > > > > > > > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > > > > > Then I tried implementing suggest as described in the following > articles > > in > > > this order > > > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > > > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > > > implemented suggesting phrases) > > > 3) > > > > > > > > > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > > > > > With no luck, after implementing each article when I run my query as > > > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > > > > > > > > > I get > > > > > > > > > 0 > > > 0 > > > > > > > > > > > > Although I have an entry for Barack Obama in my index. I am posting my > > > Solr configuration as well > > > > > > > > > > > > suggest > > >name="classname">org.apache.solr.spelling.suggest.Suggester > > >> > name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > > > entity_autocomplete > > > true > > > > > > > > > > > > > > class="org.apache.solr.handler.component.SearchHandler"> > > > > > > true > > > suggest > > > 10 > > > true > > > false > > > > > > > > > suggest > > > > > > > > > > > > It looks like a very simple job, but even after following so many > > articles, > > > I could not get it right. Any comment will be appreciated! > > > > > > Regards, > > > Salman > > > > > > > > > > > -- > > Bill Bell > > billnb...@gmail.com > > cell 720-256-8076 > > > > > > -- > -- > > Benedetti Alessandro > Visiting card - http://about.me/alessandro_benedetti > Blog - http://alexbenedetti.blogspot.co.uk > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England >
Re: AutoComplete Feature in Solr
We want to use suggester but also want to show those results closest to my lat,long... Kinda combine suggester and bq=geodist() On Mon, Oct 12, 2015 at 2:24 PM, Salman Ansari <salman.rah...@gmail.com> wrote: > Hi, > > I have been trying to get the autocomplete feature in Solr working with no > luck up to now. First I read that "suggest component" is the recommended > way as in the below article (and this is the exact functionality I am > looking for, which is to autocomplete multiple words) > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > Then I tried implementing suggest as described in the following articles in > this order > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > implemented suggesting phrases) > 3) > > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > With no luck, after implementing each article when I run my query as > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > I get > > > 0 > 0 > > > > Although I have an entry for Barack Obama in my index. I am posting my > Solr configuration as well > > > > suggest > org.apache.solr.spelling.suggest.Suggester >name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > entity_autocomplete > true > > > > class="org.apache.solr.handler.component.SearchHandler"> > > true > suggest > 10 > true > false > > > suggest > > > > It looks like a very simple job, but even after following so many articles, > I could not get it right. Any comment will be appreciated! > > Regards, > Salman > -- Bill Bell billnb...@gmail.com cell 720-256-8076
Re: AutoComplete Feature in Solr
Thanks guys, I was able to make it work using your articles. The key point was mentioned in one of the articles which was that suggestion component is preconfigured in techproducts sample. I started my work from there and tweaked it to suit my needs. Thanks a lot! One thing still remaining, I don't find the support for "suggest" is Solr.NET. What I found is that we should use Spell check but that is not the recommended option as per the articles. Spell Check component in Solr.NET will use /spell component while I have configured suggestions using /suggest component. It is easy to handle it myself as well but I was just wondering if Solr.NET supports suggest component somehow. Regards, Salman On Tue, Oct 13, 2015 at 2:39 PM, Alessandro Benedetti < benedetti.ale...@gmail.com> wrote: > As Erick suggested you are reading a really old way to provide the > autocomplete feature ! > Please take a read to the docs Erick linked and to my blog as well. > It will definitely give you more insight about the Autocomplete world ! > > Cheers > > [1] http://alexbenedetti.blogspot.co.uk/2015/07/solr-you-complete-me.html > > On 12 October 2015 at 21:24, Salman Ansari <salman.rah...@gmail.com> > wrote: > > > Hi, > > > > I have been trying to get the autocomplete feature in Solr working with > no > > luck up to now. First I read that "suggest component" is the recommended > > way as in the below article (and this is the exact functionality I am > > looking for, which is to autocomplete multiple words) > > > > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > > > Then I tried implementing suggest as described in the following articles > in > > this order > > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > > implemented suggesting phrases) > > 3) > > > > > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > > > With no luck, after implementing each article when I run my query as > > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > > > > > I get > > > > > > 0 > > 0 > > > > > > > > Although I have an entry for Barack Obama in my index. I am posting my > > Solr configuration as well > > > > > > > > suggest > > org.apache.solr.spelling.suggest.Suggester > >> name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > > entity_autocomplete > > true > > > > > > > > > class="org.apache.solr.handler.component.SearchHandler"> > > > > true > > suggest > > 10 > > true > > false > > > > > > suggest > > > > > > > > It looks like a very simple job, but even after following so many > articles, > > I could not get it right. Any comment will be appreciated! > > > > Regards, > > Salman > > > > > > -- > -- > > Benedetti Alessandro > Visiting card - http://about.me/alessandro_benedetti > Blog - http://alexbenedetti.blogspot.co.uk > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England >
Re: AutoComplete Feature in Solr
As Erick suggested you are reading a really old way to provide the autocomplete feature ! Please take a read to the docs Erick linked and to my blog as well. It will definitely give you more insight about the Autocomplete world ! Cheers [1] http://alexbenedetti.blogspot.co.uk/2015/07/solr-you-complete-me.html On 12 October 2015 at 21:24, Salman Ansari <salman.rah...@gmail.com> wrote: > Hi, > > I have been trying to get the autocomplete feature in Solr working with no > luck up to now. First I read that "suggest component" is the recommended > way as in the below article (and this is the exact functionality I am > looking for, which is to autocomplete multiple words) > > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > Then I tried implementing suggest as described in the following articles in > this order > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > implemented suggesting phrases) > 3) > > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > With no luck, after implementing each article when I run my query as > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > I get > > > 0 > 0 > > > > Although I have an entry for Barack Obama in my index. I am posting my > Solr configuration as well > > > > suggest > org.apache.solr.spelling.suggest.Suggester >name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > entity_autocomplete > true > > > > class="org.apache.solr.handler.component.SearchHandler"> > > true > suggest > 10 > true > false > > > suggest > > > > It looks like a very simple job, but even after following so many articles, > I could not get it right. Any comment will be appreciated! > > Regards, > Salman > -- -- Benedetti Alessandro Visiting card - http://about.me/alessandro_benedetti Blog - http://alexbenedetti.blogspot.co.uk "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
AutoComplete Feature in Solr
Hi, I have been trying to get the autocomplete feature in Solr working with no luck up to now. First I read that "suggest component" is the recommended way as in the below article (and this is the exact functionality I am looking for, which is to autocomplete multiple words) http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ Then I tried implementing suggest as described in the following articles in this order 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I implemented suggesting phrases) 3) http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms With no luck, after implementing each article when I run my query as http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack I get 0 0 Although I have an entry for Barack Obama in my index. I am posting my Solr configuration as well suggest org.apache.solr.spelling.suggest.Suggester org.apache.solr.spelling.suggest.fst.FSTLookup entity_autocomplete true true suggest 10 true false suggest It looks like a very simple job, but even after following so many articles, I could not get it right. Any comment will be appreciated! Regards, Salman
Re: AutoComplete Feature in Solr
Some of the links you're looking at are quite old, and a lot has changed, assuming you're on a recent Solr version. It's usually best to look at the Solr reference guide, see: https://cwiki.apache.org/confluence/display/solr/Suggester This might also help: http://lucidworks.com/blog/2015/03/04/solr-suggester/ Best, Erick On Mon, Oct 12, 2015 at 1:24 PM, Salman Ansari <salman.rah...@gmail.com> wrote: > Hi, > > I have been trying to get the autocomplete feature in Solr working with no > luck up to now. First I read that "suggest component" is the recommended > way as in the below article (and this is the exact functionality I am > looking for, which is to autocomplete multiple words) > http://blog.trifork.com/2012/02/15/different-ways-to-make-auto-suggestions-with-solr/ > > Then I tried implementing suggest as described in the following articles in > this order > 1) https://wiki.apache.org/solr/Suggester#SearchHandler_configuration > 2) http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/ (I > implemented suggesting phrases) > 3) > http://stackoverflow.com/questions/18132819/how-to-have-solr-autocomplete-on-whole-phrase-when-query-contains-multiple-terms > > With no luck, after implementing each article when I run my query as > http://[MySolr]:8983/solr/entityStore114/suggest?spellcheck.q=Barack > > > > I get > > > 0 > 0 > > > > Although I have an entry for Barack Obama in my index. I am posting my > Solr configuration as well > > > > suggest > org.apache.solr.spelling.suggest.Suggester >name="lookupImpl">org.apache.solr.spelling.suggest.fst.FSTLookup > entity_autocomplete > true > > > > class="org.apache.solr.handler.component.SearchHandler"> > > true > suggest > 10 > true > false > > > suggest > > > > It looks like a very simple job, but even after following so many articles, > I could not get it right. Any comment will be appreciated! > > Regards, > Salman
Re: Help on autocomplete / suggester
Hi Andrea, really curious I found the province where I was born in the Solr mailing list :) Apart that , based on your requirements, it's not possible to use any suggester. You should definitely design a new Solr collection(core) for your requirements. Would be quite easy to provide those services through a new specific Solr core. Cheers 2015-09-25 13:08 GMT+01:00 Andrea Gazzarini <a.gazzar...@gmail.com>: > Sorry, in the first point I meant "prefix_search" > > Best, > Andrea > > > On 09/24/2015 11:18 AM, Andrea Gazzarini wrote: > >> Hi guys, >> as part of a customer requirement, I need to provide an autocomplete / >> suggester feature. For that reason I started looking at the Suggester >> Component. >> >> The target Solr version is not yet determined: I mean, there's another >> project in production, of the same customer, which is using Solr 4.7.1 (no >> SolrCloud, just a master with two slaves) so I guess they will extend those >> instances with additional cores, but I'm not sure about that, maybe they >> would like to migrate towards a new version / new architecture. >> >> Anyway, after reading some info [1] [2] [3] about the Suggester, and >> after trying a bit with some sample data, I'm not sure if that fits my >> needs, because the proposed suggestions must follow these criteria: >> >> * suffix search: Vi = *Vi*terbo, *Vi*cenza, *Vi*llanova (max priority) >> * infix search: Vi = A*vi*gliano, Tar*vi*sio (medium priority) >> * fuzzy (phonetic?) search: Vitr= Viterbo, Vitorchiano (lowest >> priority, this requirement could be even removed) >> >> * everything could be constrained by one or more filter queries >> * each suggestion could contain (depending on the use case) up to >> five additional attributes (other than the suggestion itself), so >> the payload provided by the Suggester couldn't be enough (or it >> would require a custom encoding of such data in that field) >> * in a couple of scenarios, the search needs to be executed on >> several fields, with different boosts (e.g. description, address, >> code) and the corresponding suggestions come from another field >> (e.g. name) >> * I don't have any incremental / delta indexing issue, the whole >> dataset is not huge, a couple of millions of database records, >> with a low grow rate, and I can recreate everything from scratch >> using the DIH >> >> Do you think this is something for the built-in Suggester? Or is this >> something that it's better to implement with a RequestHandler with >> something like (e)dismax and ngramming? >> >> Many thanks in advance >> Andrea >> >> [1] https://cwiki.apache.org/confluence/display/solr/Suggester >> [2] http://lucidworks.com/blog/solr-suggester/ >> [3] http://alexbenedetti.blogspot.it/2015/07/solr-you-complete-me.html >> >> >> >> > -- -- Benedetti Alessandro Visiting card - http://about.me/alessandro_benedetti Blog - http://alexbenedetti.blogspot.co.uk "Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry?" William Blake - Songs of Experience -1794 England
Re: Help on autocomplete / suggester
Hi Alessandro, Yes, I read a lot of posts from you about the Suggester component, including your blog, so the province name was just to catch your attention :D...just kidding, I'm living there. Many many thanks Best, Andrea On 25 Sep 2015 17:12, "Alessandro Benedetti" <benedetti.ale...@gmail.com> wrote: > Hi Andrea, > really curious I found the province where I was born in the Solr mailing > list :) > > Apart that , based on your requirements, it's not possible to use any > suggester. > You should definitely design a new Solr collection(core) for your > requirements. > Would be quite easy to provide those services through a new specific Solr > core. > > Cheers > > 2015-09-25 13:08 GMT+01:00 Andrea Gazzarini <a.gazzar...@gmail.com>: > > > Sorry, in the first point I meant "prefix_search" > > > > Best, > > Andrea > > > > > > On 09/24/2015 11:18 AM, Andrea Gazzarini wrote: > > > >> Hi guys, > >> as part of a customer requirement, I need to provide an autocomplete / > >> suggester feature. For that reason I started looking at the Suggester > >> Component. > >> > >> The target Solr version is not yet determined: I mean, there's another > >> project in production, of the same customer, which is using Solr 4.7.1 > (no > >> SolrCloud, just a master with two slaves) so I guess they will extend > those > >> instances with additional cores, but I'm not sure about that, maybe they > >> would like to migrate towards a new version / new architecture. > >> > >> Anyway, after reading some info [1] [2] [3] about the Suggester, and > >> after trying a bit with some sample data, I'm not sure if that fits my > >> needs, because the proposed suggestions must follow these criteria: > >> > >> * suffix search: Vi = *Vi*terbo, *Vi*cenza, *Vi*llanova (max priority) > >> * infix search: Vi = A*vi*gliano, Tar*vi*sio (medium priority) > >> * fuzzy (phonetic?) search: Vitr= Viterbo, Vitorchiano (lowest > >> priority, this requirement could be even removed) > >> > >> * everything could be constrained by one or more filter queries > >> * each suggestion could contain (depending on the use case) up to > >> five additional attributes (other than the suggestion itself), so > >> the payload provided by the Suggester couldn't be enough (or it > >> would require a custom encoding of such data in that field) > >> * in a couple of scenarios, the search needs to be executed on > >> several fields, with different boosts (e.g. description, address, > >> code) and the corresponding suggestions come from another field > >> (e.g. name) > >> * I don't have any incremental / delta indexing issue, the whole > >> dataset is not huge, a couple of millions of database records, > >> with a low grow rate, and I can recreate everything from scratch > >> using the DIH > >> > >> Do you think this is something for the built-in Suggester? Or is this > >> something that it's better to implement with a RequestHandler with > >> something like (e)dismax and ngramming? > >> > >> Many thanks in advance > >> Andrea > >> > >> [1] https://cwiki.apache.org/confluence/display/solr/Suggester > >> [2] http://lucidworks.com/blog/solr-suggester/ > >> [3] http://alexbenedetti.blogspot.it/2015/07/solr-you-complete-me.html > >> > >> > >> > >> > > > > > -- > -- > > Benedetti Alessandro > Visiting card - http://about.me/alessandro_benedetti > Blog - http://alexbenedetti.blogspot.co.uk > > "Tyger, tyger burning bright > In the forests of the night, > What immortal hand or eye > Could frame thy fearful symmetry?" > > William Blake - Songs of Experience -1794 England >
Re: Help on autocomplete / suggester
Sorry, in the first point I meant "prefix_search" Best, Andrea On 09/24/2015 11:18 AM, Andrea Gazzarini wrote: Hi guys, as part of a customer requirement, I need to provide an autocomplete / suggester feature. For that reason I started looking at the Suggester Component. The target Solr version is not yet determined: I mean, there's another project in production, of the same customer, which is using Solr 4.7.1 (no SolrCloud, just a master with two slaves) so I guess they will extend those instances with additional cores, but I'm not sure about that, maybe they would like to migrate towards a new version / new architecture. Anyway, after reading some info [1] [2] [3] about the Suggester, and after trying a bit with some sample data, I'm not sure if that fits my needs, because the proposed suggestions must follow these criteria: * suffix search: Vi = *Vi*terbo, *Vi*cenza, *Vi*llanova (max priority) * infix search: Vi = A*vi*gliano, Tar*vi*sio (medium priority) * fuzzy (phonetic?) search: Vitr= Viterbo, Vitorchiano (lowest priority, this requirement could be even removed) * everything could be constrained by one or more filter queries * each suggestion could contain (depending on the use case) up to five additional attributes (other than the suggestion itself), so the payload provided by the Suggester couldn't be enough (or it would require a custom encoding of such data in that field) * in a couple of scenarios, the search needs to be executed on several fields, with different boosts (e.g. description, address, code) and the corresponding suggestions come from another field (e.g. name) * I don't have any incremental / delta indexing issue, the whole dataset is not huge, a couple of millions of database records, with a low grow rate, and I can recreate everything from scratch using the DIH Do you think this is something for the built-in Suggester? Or is this something that it's better to implement with a RequestHandler with something like (e)dismax and ngramming? Many thanks in advance Andrea [1] https://cwiki.apache.org/confluence/display/solr/Suggester [2] http://lucidworks.com/blog/solr-suggester/ [3] http://alexbenedetti.blogspot.it/2015/07/solr-you-complete-me.html
Help on autocomplete / suggester
Hi guys, as part of a customer requirement, I need to provide an autocomplete / suggester feature. For that reason I started looking at the Suggester Component. The target Solr version is not yet determined: I mean, there's another project in production, of the same customer, which is using Solr 4.7.1 (no SolrCloud, just a master with two slaves) so I guess they will extend those instances with additional cores, but I'm not sure about that, maybe they would like to migrate towards a new version / new architecture. Anyway, after reading some info [1] [2] [3] about the Suggester, and after trying a bit with some sample data, I'm not sure if that fits my needs, because the proposed suggestions must follow these criteria: * suffix search: Vi = *Vi*terbo, *Vi*cenza, *Vi*llanova (max priority) * infix search: Vi = A*vi*gliano, Tar*vi*sio (medium priority) * fuzzy (phonetic?) search: Vitr= Viterbo, Vitorchiano (lowest priority, this requirement could be even removed) * everything could be constrained by one or more filter queries * each suggestion could contain (depending on the use case) up to five additional attributes (other than the suggestion itself), so the payload provided by the Suggester couldn't be enough (or it would require a custom encoding of such data in that field) * in a couple of scenarios, the search needs to be executed on several fields, with different boosts (e.g. description, address, code) and the corresponding suggestions come from another field (e.g. name) * I don't have any incremental / delta indexing issue, the whole dataset is not huge, a couple of millions of database records, with a low grow rate, and I can recreate everything from scratch using the DIH Do you think this is something for the built-in Suggester? Or is this something that it's better to implement with a RequestHandler with something like (e)dismax and ngramming? Many thanks in advance Andrea [1] https://cwiki.apache.org/confluence/display/solr/Suggester [2] http://lucidworks.com/blog/solr-suggester/ [3] http://alexbenedetti.blogspot.it/2015/07/solr-you-complete-me.html
Re: multiple but identical suggestions in autocomplete
You will need to call this service from UI as you are calling suggester component currently. (may be on every key-press event in text box). You will pass required parameters too. Service will internally form a solr suggester query and query Solr. From the returned response it will keep only unique suggestions from top N suggestions and return suggestions to UI. - Nutch Solr User The ultimate search engine would basically understand everything in the world, and it would always give you the right thing. -- View this message in context: http://lucene.472066.n3.nabble.com/multiple-but-identical-suggestions-in-autocomplete-tp4220055p4220953.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: multiple but identical suggestions in autocomplete
Hello Nutch Solr user, You are right I use DocumentDictionaryFactory as you can see in my solrconfig file searchComponent name=suggest class=solr.SuggestComponent lst name=suggester str name=namesuggest_publisher/str str name=lookupImplAnalyzingInfixLookupFactory/str str name=dictionaryImplDocumentDictionaryFactory/str str name=fieldpublisher/str str name=suggestAnalyzerFieldTypetext_hu_suggest_ngram/str str name=indexPathsuggester_infix_dir_publisher/str str name=weightFieldprice/str str name=builOnStartupfalse/str str name=buildOnCommitfalse/str /lst /searchComponent You wrote that you you have developed a service between the ui and solr. How can I use that one if I use javascript / ajax on the client side? Thanks, Roland 2015-08-04 16:25 GMT+02:00 Nutch Solr User nutchsolru...@gmail.com: May be you are using DocumentDictionaryFactory because HighFrequencyDictionaryFactory will never return duplicate duplicate terms. We also had same problem with *DocumentDictionaryFactory + AnalyzingInfixSuggester* We have created one service between UI and Solr which groups duplicate suggestions. and returns unique list to UI with only contains unique suggestions. - Nutch Solr User The ultimate search engine would basically understand everything in the world, and it would always give you the right thing. -- View this message in context: http://lucene.472066.n3.nabble.com/multiple-but-identical-suggestions-in-autocomplete-tp4220055p4220727.html Sent from the Solr - User mailing list archive at Nabble.com. -- https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/huSzűcs Roland https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/huIsmerkedjünk meg a Linkedin https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/hu -en https://bookandwalk.hu/ÜgyvezetőTelefon: +36 1 210 81 13Bookandwalk.hu https://bokandwalk.hu/
Re: multiple but identical suggestions in autocomplete
May be you are using DocumentDictionaryFactory because HighFrequencyDictionaryFactory will never return duplicate duplicate terms. We also had same problem with *DocumentDictionaryFactory + AnalyzingInfixSuggester* We have created one service between UI and Solr which groups duplicate suggestions. and returns unique list to UI with only contains unique suggestions. - Nutch Solr User The ultimate search engine would basically understand everything in the world, and it would always give you the right thing. -- View this message in context: http://lucene.472066.n3.nabble.com/multiple-but-identical-suggestions-in-autocomplete-tp4220055p4220727.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Fast autocomplete for large dataset
Thank you Eric for your reply. If I understand it seems that these approaches are using index to hold terms. As the index grows bigger, it can be a performance issues. Is it right? Please can you check this article http://www.norconex.com/serving-autocomplete-suggestions-fast/ to see what I mean? Thank you. Regards Olivier 2015-08-01 17:42 GMT+02:00 Erick Erickson erickerick...@gmail.com: Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Re: Fast autocomplete for large dataset
Not really. There's no need to use ngrams as the article suggests if the terms component does what you need. Which is why I asked you about what autocomplete means in your context. Which you have not clarified. Have you even looked at terms component? Especially the terms.prefix option? Terms component has it's limitations, but performance isn't one of them. The suggesters mentioned in the article have other limitations. It's really useless to discuss those limitations, though, until the problem you're trying to solve is clearly stated. On Aug 1, 2015 1:01 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric for your reply. If I understand it seems that these approaches are using index to hold terms. As the index grows bigger, it can be a performance issues. Is it right? Please can you check this article http://www.norconex.com/serving-autocomplete-suggestions-fast/ to see what I mean? Thank you. Regards Olivier 2015-08-01 17:42 GMT+02:00 Erick Erickson erickerick...@gmail.com: Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Re: Fast autocomplete for large dataset
Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Re: Fast autocomplete for large dataset
Thank you Eric, I would like to implement an autocomplete for large dataset. The autocomplete should show the phrase or the question the user want as the user types. The requirement is that the autocomplete should be fast (not slowdown by the volume of data as dataset become bigger), and easy to maintain. The autocomplete can have its own Solr server. It is an autocomplete like others but it should be only fast and easy to maintain. What is the limitations of suggesters mentioned in the article? Thank you. Regards Olivier 2015-08-01 19:41 GMT+02:00 Erick Erickson erickerick...@gmail.com: Not really. There's no need to use ngrams as the article suggests if the terms component does what you need. Which is why I asked you about what autocomplete means in your context. Which you have not clarified. Have you even looked at terms component? Especially the terms.prefix option? Terms component has it's limitations, but performance isn't one of them. The suggesters mentioned in the article have other limitations. It's really useless to discuss those limitations, though, until the problem you're trying to solve is clearly stated. On Aug 1, 2015 1:01 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric for your reply. If I understand it seems that these approaches are using index to hold terms. As the index grows bigger, it can be a performance issues. Is it right? Please can you check this article http://www.norconex.com/serving-autocomplete-suggestions-fast/ to see what I mean? Thank you. Regards Olivier 2015-08-01 17:42 GMT+02:00 Erick Erickson erickerick...@gmail.com: Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Fast autocomplete for large dataset
Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Re: Fast autocomplete for large dataset
Thank you Eric for your replies and the link. Regards Olivier 2015-08-02 3:47 GMT+02:00 Erick Erickson erickerick...@gmail.com: Here's some background: http://lucidworks.com/blog/solr-suggester/ Basically, the limitation is that to build the suggester all docs in the index need to be read to pull out the stored field and build either the FST or the sidecar Lucene index, which can be a _very_ costly operation (as in minutes/hours for a large dataset). bq: The requirement is that the autocomplete should be fast (not slowdown by the volume of data as dataset become bigger) Well, in some alternate universe this may be possible. But the larger the corpus the slower the processing will be, there's just no way around that. Whether it's fast enough for your application is a better question ;). Best, Erick On Sat, Aug 1, 2015 at 2:05 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric, I would like to implement an autocomplete for large dataset. The autocomplete should show the phrase or the question the user want as the user types. The requirement is that the autocomplete should be fast (not slowdown by the volume of data as dataset become bigger), and easy to maintain. The autocomplete can have its own Solr server. It is an autocomplete like others but it should be only fast and easy to maintain. What is the limitations of suggesters mentioned in the article? Thank you. Regards Olivier 2015-08-01 19:41 GMT+02:00 Erick Erickson erickerick...@gmail.com: Not really. There's no need to use ngrams as the article suggests if the terms component does what you need. Which is why I asked you about what autocomplete means in your context. Which you have not clarified. Have you even looked at terms component? Especially the terms.prefix option? Terms component has it's limitations, but performance isn't one of them. The suggesters mentioned in the article have other limitations. It's really useless to discuss those limitations, though, until the problem you're trying to solve is clearly stated. On Aug 1, 2015 1:01 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric for your reply. If I understand it seems that these approaches are using index to hold terms. As the index grows bigger, it can be a performance issues. Is it right? Please can you check this article http://www.norconex.com/serving-autocomplete-suggestions-fast/ to see what I mean? Thank you. Regards Olivier 2015-08-01 17:42 GMT+02:00 Erick Erickson erickerick...@gmail.com: Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
Re: Fast autocomplete for large dataset
Here's some background: http://lucidworks.com/blog/solr-suggester/ Basically, the limitation is that to build the suggester all docs in the index need to be read to pull out the stored field and build either the FST or the sidecar Lucene index, which can be a _very_ costly operation (as in minutes/hours for a large dataset). bq: The requirement is that the autocomplete should be fast (not slowdown by the volume of data as dataset become bigger) Well, in some alternate universe this may be possible. But the larger the corpus the slower the processing will be, there's just no way around that. Whether it's fast enough for your application is a better question ;). Best, Erick On Sat, Aug 1, 2015 at 2:05 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric, I would like to implement an autocomplete for large dataset. The autocomplete should show the phrase or the question the user want as the user types. The requirement is that the autocomplete should be fast (not slowdown by the volume of data as dataset become bigger), and easy to maintain. The autocomplete can have its own Solr server. It is an autocomplete like others but it should be only fast and easy to maintain. What is the limitations of suggesters mentioned in the article? Thank you. Regards Olivier 2015-08-01 19:41 GMT+02:00 Erick Erickson erickerick...@gmail.com: Not really. There's no need to use ngrams as the article suggests if the terms component does what you need. Which is why I asked you about what autocomplete means in your context. Which you have not clarified. Have you even looked at terms component? Especially the terms.prefix option? Terms component has it's limitations, but performance isn't one of them. The suggesters mentioned in the article have other limitations. It's really useless to discuss those limitations, though, until the problem you're trying to solve is clearly stated. On Aug 1, 2015 1:01 PM, Olivier Austina olivier.aust...@gmail.com wrote: Thank you Eric for your reply. If I understand it seems that these approaches are using index to hold terms. As the index grows bigger, it can be a performance issues. Is it right? Please can you check this article http://www.norconex.com/serving-autocomplete-suggestions-fast/ to see what I mean? Thank you. Regards Olivier 2015-08-01 17:42 GMT+02:00 Erick Erickson erickerick...@gmail.com: Well, defining what you mean by autocomplete would be a start. If it's just a user types some letters and you suggest the next N terms in the list, TermsComponent will fix you right up. If it's more complicated, the AutoSuggest functionality might help. If it's correcting spelling, there's the spellchecker. Best, Erick On Sat, Aug 1, 2015 at 10:00 AM, Olivier Austina olivier.aust...@gmail.com wrote: Hi, I am looking for a fast and easy to maintain way to do autocomplete for large dataset in solr. I heard about Ternary Search Tree (TST) https://en.wikipedia.org/wiki/Ternary_search_tree. But I would like to know if there is something I missed such as best practice, Solr new feature. Any suggestion is welcome. Thank you. Regards Olivier
multiple but identical suggestions in autocomplete
Hello Guys, I use SOLR 5.2.1 and the relatively new solr.SuggestComponent. It worked fine at the beginning. I use this function to auto-complete the publisher names. I have 3000 documents and 80 publishers. When I use the autocomplete feature and I get back the name of the publishers matched as many times as many book titles they published. If suggest.q=Har and Harlequin publisher has 100 documents I get back a json with 100 suggestions with the same publisher name. Obviously it is not my intention. I would like to get back the matched publisher name once and later I will use a filter query to the selected publisher name. Any Idea how can I get identical suggestions only once? Is there any parameter I can set in solrconfig.xml to solve this? Thanks in advance, -- https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/huSzűcs Roland https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/huIsmerkedjünk meg a Linkedin https://www.linkedin.com/pub/roland-sz%C5%B1cs/28/226/24/hu -en https://bookandwalk.hu/ÜgyvezetőTelefon: +36 1 210 81 13Bookandwalk.hu https://bokandwalk.hu/
Need autocomplete on whole phrase for multiple words .
Hi solrExperts, Need autocomplete on whole phrase for multiple words . When I typed *br, *the results are brad , brad pitt but I need only brad pitt to come. I’m using shinglefilterfactory + terms component for autocomplete feature , the query is something like http://localhost:8080/solr/actors/terms?terms.fl=content_autosuggestomitHeader=trueterms.sort=indexindent=truewt=jsonjson.nl=mapterms.prefix=bra below is my shema configuration : field name=actors type=text_auto indexed=true stored=true multiValued=true/ fieldType class=solr.TextField name=text_auto analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt enablePositionIncrements=true/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=2 outputUnigrams=true outputUnigramsIfNoShingles=false tokenSeparator= fillerToken=_/ filter class=solr.PatternReplaceFilterFactory pattern=_ replacement= replace=all/ filter class=solr.RemoveDuplicatesTokenFilterFactory/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt enablePositionIncrements=true/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=2 outputUnigrams=false outputUnigramsIfNoShingles=false tokenSeparator= fillerToken=_/ filter class=solr.PatternReplaceFilterFactory pattern=_ replacement= replace=all/ filter class=solr.RemoveDuplicatesTokenFilterFactory/ /analyzer /fieldType Thanks Regards, Vamshi
Solr Suggester Autocomplete Working Example
Hi, I'm am wondering if anyone can point me to a website that user Solr's Suggester or Autocomplete or whatever you call it. I am looking for something that is closer to the default provided in the examples, but is also used commercially. I have a local Solr installation that is on an intranet. (Sorry I cannot post it here.) Unfortunately, the suggestions it provides does not seem to be OK. By this I mean in comparison to Google, which I know does not use Solr. For example, when I type the string sto into my installation, I get the suggested values like storag - which is not a complete word i.e. it misses the 'e' in the end. On the other hand when I use Google, I get complete words like stock market or stopwatch etc. I know Google does not use Solr. I also know that I do not have the capability to do a lot of customizations to Solr that are much beyond the defaults and changing a few settings. Hence I am curious if there is a website out there that uses Suggester or Autocomplete where I can compare the capabilities with my own. Thank you -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Suggester-Autocomplete-Working-Example-tp4183493.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Suggester Autocomplete Working Example
Please go ahead and play with autocomplete on safaribooksonline.com/home - if you are not a subscriber you will have to sign up for a free trial. We use the AnalyzingInfixSuggester. From your description, it sounds as if you are building completions from a field that you also use for searching -- maybe it is stemmed, and that's why you are seeing the weird partial words. To get good results from the suggester you will probably need to set up a special field to use as a source of suggestions that uses appropriate text analysis. -Mike On 2/2/2015 11:26 AM, O. Olson wrote: Hi, I'm am wondering if anyone can point me to a website that user Solr's Suggester or Autocomplete or whatever you call it. I am looking for something that is closer to the default provided in the examples, but is also used commercially. I have a local Solr installation that is on an intranet. (Sorry I cannot post it here.) Unfortunately, the suggestions it provides does not seem to be OK. By this I mean in comparison to Google, which I know does not use Solr. For example, when I type the string sto into my installation, I get the suggested values like storag - which is not a complete word i.e. it misses the 'e' in the end. On the other hand when I use Google, I get complete words like stock market or stopwatch etc. I know Google does not use Solr. I also know that I do not have the capability to do a lot of customizations to Solr that are much beyond the defaults and changing a few settings. Hence I am curious if there is a website out there that uses Suggester or Autocomplete where I can compare the capabilities with my own. Thank you -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Suggester-Autocomplete-Working-Example-tp4183493.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Suggester Autocomplete Working Example
On 2 February 2015 at 11:26, O. Olson olson_...@yahoo.it wrote: I also know that I do not have the capability to do a lot of customizations to Solr that are much beyond the defaults and changing a few settings. Actually, you have a capability to do unbelievable level of customization in Solr, starting from schema definition and down to writing custom components in Java. Or even completely rebuilding Solr the way you want from sources. Or was that a reference to your current skills rather than than Solr's? I think that should be fixable as well. Just keep learning and asking questions. We'll try to help. As to the suggester, it may make sense to explain what kind of text you are providing and what results you might be expecting. A bit more details that you've given already. There are several different implementations, each with its own trade-offs. Regards, Alex. Sign up for my Solr resources newsletter at http://www.solr-start.com/
Re: Solr Suggester Autocomplete Working Example
Thank you Michael. I will look at safaribooksonline.com later today when I create my account. I am not sure how to use AnalyzingInfixSuggester. I googled a bit, and I can find the source code, but not how to use it. You are perfectly correct when you say that I am using a field also used for searching and which has been stemmed. I need to look into setting up another field for the suggester. I will post here when I have questions about this. Thanks again. Michael Sokolov-3 wrote Please go ahead and play with autocomplete on safaribooksonline.com/home - if you are not a subscriber you will have to sign up for a free trial. We use the AnalyzingInfixSuggester. From your description, it sounds as if you are building completions from a field that you also use for searching -- maybe it is stemmed, and that's why you are seeing the weird partial words. To get good results from the suggester you will probably need to set up a special field to use as a source of suggestions that uses appropriate text analysis. -Mike -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Suggester-Autocomplete-Working-Example-tp4183493p4183530.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr Suggester Autocomplete Working Example
Alexandre Rafalovitch wrote Actually, you have a capability to do unbelievable level of customization in Solr, starting from schema definition and down to writing custom components in Java. Or even completely rebuilding Solr the way you want from sources. Or was that a reference to your current skills rather than than Solr's? I think that should be fixable as well. Just keep learning and asking questions. We'll try to help. As to the suggester, it may make sense to explain what kind of text you are providing and what results you might be expecting. A bit more details that you've given already. There are several different implementations, each with its own trade-offs. Regards, Alex. Sorry Alex, I am just a bit dumb. That reference was regarding my skills not Solr's. I think Michael pointed out one of my problems i.e. I was using the Search field that had been stemmed. I will look at creating an alternate field just for the suggester. Thank you. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Suggester-Autocomplete-Working-Example-tp4183493p4183532.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Still not able to get my autoComplete component to work in a distributed
environment. Works fine on a non-distributed system. Also, on the distributed
system, if I include distrib=false, it works.
I have tried shards.qt and shards parameters, but they make no difference. I
should add, I am running SolrCloud and ZooKeeper, if that makes any difference.
I have played around with this quite a bit, but nothing seems to work.
When I add shards.qt=/ac {the name of the request handler}, I get an error in
the solr logs. It simply states: java.lang.NullPointerException. That's it
nothing more. This is listed as logger SolrCore and SolrDispatchFilter.
Any ideas, suggestions on how I can troubleshoot and find the problem? Is there
something specific I should look for?
Please find attached text file with relevant information from schema.xml and
sorlconfig.xml.
Any help greatly appreciated! Thanks,
-Charles
- Original Message -
From: Erick Erickson erickerick...@gmail.com
To: solr-user@lucene.apache.org
Sent: Tuesday, December 30, 2014 6:07:13 PM
Subject: Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Did you try the shards parameter? See:
https://cwiki.apache.org/confluence/display/solr/Spell+Checking#SpellChecking-DistributedSpellCheck
On Tue, Dec 30, 2014 at 2:20 PM, Charles Sanders csand...@redhat.com wrote:
I'm running Solr 4.8 in a distributed environment (2 shards). I have added
the spellcheck component to my request handler. In my test system, which is
not distributed, it works. But when I move it to the Dev box, which is
distributed, 2 shards, it is not working. Is there something additional I
must do to get this to work in a distributed environment?
requestHandler default=true name=standard class=solr.SearchHandler
!-- default values for query parameters can be specified, these
will be overridden by parameters in the request
--
lst name=defaults
str name=echoParamsexplicit/str
int name=rows10/int
str name=dfallText/str
!-- default autocomplete settings for this search request handler --
str name=spellchecktrue/str
str name=spellcheck.dictionaryandreasAutoComplete/str
str name=spellcheck.onlyMorePopulartrue/str
str name=spellcheck.count5/str
str name=spellcheck.collatetrue/str
str name=spellcheck.maxCollations5/str
/lst
arr name=last-components
strautoComplete/str
/arr
/requestHandler
searchComponent name=autoComplete class=solr.SpellCheckComponent
lst name=spellchecker
str name=nameandreasAutoComplete/str
str name=classnameorg.apache.solr.spelling.suggest.Suggester/str
str
name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookupFactory/str
str name=fieldsugg_allText/str
str name=buildOnCommittrue/str
float name=threshold.005/float
str name=queryAnalyzerFieldTypetext_suggest/str
/lst
/searchComponent
Any help greatly appreciated! Thanks,
-Charles
* Schema.xml ***
field name=issue_suggest type=text_suggest indexed=true stored=false/
field name=sugg_allText type=text_suggest indexed=true
multiValued=true stored=false/
fieldType name=text_suggest class=solr.TextField
positionIncrementGap=100
analyzer type=index
tokenizer class=solr.StandardTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
/analyzer
analyzer type=query
tokenizer class=solr.StandardTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
/analyzer
/fieldType
Solrconfig.xml ***
!-- Auto-Complete component --
searchComponent name=autoComplete class=solr.SpellCheckComponent
lst name=spellchecker
str name=nameandreasAutoComplete/str
str
name=classnameorg.apache.solr.spelling.suggest.Suggester/str
str
name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookupFactory/str
str name=fieldsugg_allText/str
str name=buildOnCommittrue/str
float name=threshold.005/float
str name=queryAnalyzerFieldTypetext_suggest/str
/lst
lst name=spellchecker
str name=namerecommendationsAutoComplete/str
str
name=classnameorg.apache.solr.spelling.suggest.Suggester/str
str
name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookupFactory/str
str name=fieldissue_suggest/str
str name=buildOnCommittrue/str
float name=threshold.005/float
str name=queryAnalyzerFieldTypetext_suggest/str
/lst
/searchComponent
requestHandler name=/ac class=solr.SearchHandler
lst name=defaults
str name=spellchecktrue/str
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
On 1/1/2015 1:09 PM, Meraj A. Khan wrote: When running SolrCloud do you even have to include the shards parameter ,shouldnt only shards.qt parameter suffice? If you are using SolrCloud, no shards parameter is required ... all queries sent to either the collection or any shard replica will automatically use all shards. You *can* use the shards parameter if you only want to query a subset of your shards, or distrib=false if you want to only query the specific shard replica where you sent the request. If it's not SolrCloud, there is no distributed search without the shards parameter. If you're using the /select handler, then shards.qt is not necessary at all. I do not know what SolrCloud does with handlers on distributed requests, whether it uses the same handler name for those requests, or uses /select by default like non-cloud does. Thanks, Shawn
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Shawn, When running SolrCloud do you even have to include the shards parameter ,shouldnt only shards.qt parameter suffice? On Dec 30, 2014 7:17 PM, Shawn Heisey apa...@elyograg.org wrote: On 12/30/2014 5:03 PM, Charles Sanders wrote: Thanks for the suggestion. I did not do that originally because the documentation states: This parameter is not required for the /select request handler. Which is what I am using. But I gave it a go, even though I'm not certain of the shard names. Now I have a NPE. solr/collection1/select?q=kernel+prows=1wt=jsonindent=trueshards.qt=/acshards=shard1,shard2 If this is not SolrCloud, then the shards parameter must include most of the full base URL for each shard that you will be querying. You can only use a bare shard name if you're running SolrCloud. The shards.qt parameter that you have used means that when the shards are consulted, the /ac handler will be used rather than /select. Here's an example of a shards parameter that will combine results from three cores on two machines. When not running SolrCloud, this is how you do distributed searching: shards= idxa2.example.com:8981/solr/ai-inclive,idxa1.example.com:8981/solr/ai-0live,idxa2.example.com:8981/solr/ai-1live SolrCloud hides almost all of this complexity. Thanks, Shawn
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Got it. Thanks for your help everyone. - Original Message - From: Shawn Heisey apa...@elyograg.org To: solr-user@lucene.apache.org Sent: Tuesday, December 30, 2014 7:16:59 PM Subject: Re: SpellCheck (AutoComplete) Not Working In Distributed Environment On 12/30/2014 5:03 PM, Charles Sanders wrote: Thanks for the suggestion. I did not do that originally because the documentation states: This parameter is not required for the /select request handler. Which is what I am using. But I gave it a go, even though I'm not certain of the shard names. Now I have a NPE. solr/collection1/select?q=kernel+prows=1wt=jsonindent=trueshards.qt=/acshards=shard1,shard2 If this is not SolrCloud, then the shards parameter must include most of the full base URL for each shard that you will be querying. You can only use a bare shard name if you're running SolrCloud. The shards.qt parameter that you have used means that when the shards are consulted, the /ac handler will be used rather than /select. Here's an example of a shards parameter that will combine results from three cores on two machines. When not running SolrCloud, this is how you do distributed searching: shards=idxa2.example.com:8981/solr/ai-inclive,idxa1.example.com:8981/solr/ai-0live,idxa2.example.com:8981/solr/ai-1live SolrCloud hides almost all of this complexity. Thanks, Shawn
SpellCheck (AutoComplete) Not Working In Distributed Environment
I'm running Solr 4.8 in a distributed environment (2 shards). I have added the spellcheck component to my request handler. In my test system, which is not distributed, it works. But when I move it to the Dev box, which is distributed, 2 shards, it is not working. Is there something additional I must do to get this to work in a distributed environment? requestHandler default=true name=standard class=solr.SearchHandler !-- default values for query parameters can be specified, these will be overridden by parameters in the request -- lst name=defaults str name=echoParamsexplicit/str int name=rows10/int str name=dfallText/str !-- default autocomplete settings for this search request handler -- str name=spellchecktrue/str str name=spellcheck.dictionaryandreasAutoComplete/str str name=spellcheck.onlyMorePopulartrue/str str name=spellcheck.count5/str str name=spellcheck.collatetrue/str str name=spellcheck.maxCollations5/str /lst arr name=last-components strautoComplete/str /arr /requestHandler searchComponent name=autoComplete class=solr.SpellCheckComponent lst name=spellchecker str name=nameandreasAutoComplete/str str name=classnameorg.apache.solr.spelling.suggest.Suggester/str str name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookupFactory/str str name=fieldsugg_allText/str str name=buildOnCommittrue/str float name=threshold.005/float str name=queryAnalyzerFieldTypetext_suggest/str /lst /searchComponent Any help greatly appreciated! Thanks, -Charles
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Did you try the shards parameter? See: https://cwiki.apache.org/confluence/display/solr/Spell+Checking#SpellChecking-DistributedSpellCheck On Tue, Dec 30, 2014 at 2:20 PM, Charles Sanders csand...@redhat.com wrote: I'm running Solr 4.8 in a distributed environment (2 shards). I have added the spellcheck component to my request handler. In my test system, which is not distributed, it works. But when I move it to the Dev box, which is distributed, 2 shards, it is not working. Is there something additional I must do to get this to work in a distributed environment? requestHandler default=true name=standard class=solr.SearchHandler !-- default values for query parameters can be specified, these will be overridden by parameters in the request -- lst name=defaults str name=echoParamsexplicit/str int name=rows10/int str name=dfallText/str !-- default autocomplete settings for this search request handler -- str name=spellchecktrue/str str name=spellcheck.dictionaryandreasAutoComplete/str str name=spellcheck.onlyMorePopulartrue/str str name=spellcheck.count5/str str name=spellcheck.collatetrue/str str name=spellcheck.maxCollations5/str /lst arr name=last-components strautoComplete/str /arr /requestHandler searchComponent name=autoComplete class=solr.SpellCheckComponent lst name=spellchecker str name=nameandreasAutoComplete/str str name=classnameorg.apache.solr.spelling.suggest.Suggester/str str name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookupFactory/str str name=fieldsugg_allText/str str name=buildOnCommittrue/str float name=threshold.005/float str name=queryAnalyzerFieldTypetext_suggest/str /lst /searchComponent Any help greatly appreciated! Thanks, -Charles
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Thanks for the suggestion.
I did not do that originally because the documentation states:
This parameter is not required for the /select request handler.
Which is what I am using. But I gave it a go, even though I'm not certain of
the shard names. Now I have a NPE.
solr/collection1/select?q=kernel+prows=1wt=jsonindent=trueshards.qt=/acshards=shard1,shard2
{
responseHeader:{
status:500,
QTime:12,
params:{
shards:shard1,shard2,
indent:true,
shards.qt:/ac,
q:kernel p,
wt:json,
rows:1}},
error:{
trace:java.lang.NullPointerException\n\tat
org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:901)\n\tat
org.apache.solr.handler.component.QueryComponent.handleRegularResponses(QueryComponent.java:686)\n\tat
org.apache.solr.handler.component.QueryComponent.handleResponses(QueryComponent.java:665)\n\tat
org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:325)\n\tat
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)\n\tat
org.apache.solr.core.SolrCore.execute(SolrCore.java:1952)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:787)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:431)\n\tat
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)\n\tat
com.lucid.servlet.LweSolrDispatchFilter.doFilter(LweSolrDispatchFilter.java:202)\n\tat
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)\n\tat
com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)\n\tat
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)\n\tat
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)\n\tat
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1337)\n\tat
org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:212)\n\tat
org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:179)\n\tat
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1337)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)\n\tat
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)\n\tat
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:233)\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065)\n\tat
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413)\n\tat
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192)\n\tat
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999)\n\tat
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)\n\tat
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)\n\tat
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)\n\tat
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111)\n\tat
org.eclipse.jetty.server.Server.handle(Server.java:351)\n\tat
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454)\n\tat
org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47)\n\tat
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:890)\n\tat
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:944)\n\tat
org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:634)\n\tat
org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230)\n\tat
org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66)\n\tat
org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254)\n\tat
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)\n\tat
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)\n\tat
java.lang.Thread.run(Thread.java:744)\n,
code:500}}
- Original Message -
From: Erick Erickson erickerick...@gmail.com
To: solr-user@lucene.apache.org
Sent: Tuesday, December 30, 2014 6:07:13 PM
Subject: Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
Did you try the shards parameter? See:
https://cwiki.apache.org/confluence/display/solr/Spell+Checking#SpellChecking-DistributedSpellCheck
On Tue, Dec 30, 2014 at 2:20 PM, Charles Sanders csand
Re: SpellCheck (AutoComplete) Not Working In Distributed Environment
On 12/30/2014 5:03 PM, Charles Sanders wrote: Thanks for the suggestion. I did not do that originally because the documentation states: This parameter is not required for the /select request handler. Which is what I am using. But I gave it a go, even though I'm not certain of the shard names. Now I have a NPE. solr/collection1/select?q=kernel+prows=1wt=jsonindent=trueshards.qt=/acshards=shard1,shard2 If this is not SolrCloud, then the shards parameter must include most of the full base URL for each shard that you will be querying. You can only use a bare shard name if you're running SolrCloud. The shards.qt parameter that you have used means that when the shards are consulted, the /ac handler will be used rather than /select. Here's an example of a shards parameter that will combine results from three cores on two machines. When not running SolrCloud, this is how you do distributed searching: shards=idxa2.example.com:8981/solr/ai-inclive,idxa1.example.com:8981/solr/ai-0live,idxa2.example.com:8981/solr/ai-1live SolrCloud hides almost all of this complexity. Thanks, Shawn
Re: Best practice: Autosuggest/autocomplete vs. real search
The goal is to ensure that suggestions from autocomplete are actually terms in the main index, so that the suggestions will actually result in matches. You've considered expanding the main index by adding the suggestion n-grams to it, but it would probably be better to alter your suggester so that it produces only tokens that are in the main index. I think this is basically how all the Suggester implementations are designed to work already; are you using one of those, or are you using the TermsComponent, or something else? -Mike On 11/10/14 2:54 AM, Thomas Michael Engelke wrote: We're using Solr as a backend for an ECommerce site/system. The Solr index stores products with selected attributes, as well as a dedicated field for autocomplete suggestions (Done via AJAX request when typing in the search box without pressing return). The autosuggest field is supplied by copyField directives from certain select product attribute fields (description and/or name mostly). It uses EdgeNGramFilterFactory to complete words not yet typed completely, and it works quite well. However, we come across an issue with a disconnect between the autosuggest results and results of a normal search, that is, a query over the full fields of the product. Let's say there are products that are called motor. - When autosuggesting, typing mot autosuggests all products with motor, because the EdgeNGram created m, mo, mot, moto and motor, respectively, and it matches. - When searching for mot, however (i.e. pressing enter when seeing the autosuggestions), it doesn't find any products. The autosuggest field is not part of the real search, and no product attribute contains mot as a word. One obvious solution would be to incorporate the autosuggest field into the real search, however, this adds many tokens to the index that aren't really part of the products indexed and makes for strange search results, for example when an NGram is also a word, but the record itself does contain the search term only as part of a word. Are there clever solutions to this problem?
Re: Best practice: Autosuggest/autocomplete vs. real search
It wouldn’t be easy if in the site you’ll ensure that only terms are submitted to the actual search? In app I worked some time ago the default behavior of the Javascript component used for autocompletion was to first autocomplete the term in the input and then submit the query against the backend. I know this is not what you’ve asked for but could work? I’m just firing a bullet in the air here! :-) On Nov 10, 2014, at 8:37 AM, Michael Sokolov msoko...@safaribooksonline.com wrote: The goal is to ensure that suggestions from autocomplete are actually terms in the main index, so that the suggestions will actually result in matches. You've considered expanding the main index by adding the suggestion n-grams to it, but it would probably be better to alter your suggester so that it produces only tokens that are in the main index. I think this is basically how all the Suggester implementations are designed to work already; are you using one of those, or are you using the TermsComponent, or something else? -Mike On 11/10/14 2:54 AM, Thomas Michael Engelke wrote: We're using Solr as a backend for an ECommerce site/system. The Solr index stores products with selected attributes, as well as a dedicated field for autocomplete suggestions (Done via AJAX request when typing in the search box without pressing return). The autosuggest field is supplied by copyField directives from certain select product attribute fields (description and/or name mostly). It uses EdgeNGramFilterFactory to complete words not yet typed completely, and it works quite well. However, we come across an issue with a disconnect between the autosuggest results and results of a normal search, that is, a query over the full fields of the product. Let's say there are products that are called motor. - When autosuggesting, typing mot autosuggests all products with motor, because the EdgeNGram created m, mo, mot, moto and motor, respectively, and it matches. - When searching for mot, however (i.e. pressing enter when seeing the autosuggestions), it doesn't find any products. The autosuggest field is not part of the real search, and no product attribute contains mot as a word. One obvious solution would be to incorporate the autosuggest field into the real search, however, this adds many tokens to the index that aren't really part of the products indexed and makes for strange search results, for example when an NGram is also a word, but the record itself does contain the search term only as part of a word. Are there clever solutions to this problem?
Re: Best practice: Autosuggest/autocomplete vs. real search
The dedicated autosuggest field is not used by a suggester component, instead we just directly query it (/select). I'm trying to read my way into how the suggesters work, and toying around with some configurations (For instance from here: http://www.andornot.com/blog/post/Advanced-autocomplete-with-Solr-Ngrams-and-Twitters-typeaheadjs.aspx). Compared to how you can analyze search result through the Solr backend, the analysis of suggester results seems to be sorely lacking. Am 10.11.2014 14:37 schrieb Michael Sokolov: The goal is to ensure that suggestions from autocomplete are actually terms in the main index, so that the suggestions will actually result in matches. You've considered expanding the main index by adding the suggestion n-grams to it, but it would probably be better to alter your suggester so that it produces only tokens that are in the main index. I think this is basically how all the Suggester implementations are designed to work already; are you using one of those, or are you using the TermsComponent, or something else? -Mike On 11/10/14 2:54 AM, Thomas Michael Engelke wrote: We're using Solr as a backend for an ECommerce site/system. The Solr index stores products with selected attributes, as well as a dedicated field for autocomplete suggestions (Done via AJAX request when typing in the search box without pressing return). The autosuggest field is supplied by copyField directives from certain select product attribute fields (description and/or name mostly). It uses EdgeNGramFilterFactory to complete words not yet typed completely, and it works quite well. However, we come across an issue with a disconnect between the autosuggest results and results of a normal search, that is, a query over the full fields of the product. Let's say there are products that are called motor. - When autosuggesting, typing mot autosuggests all products with motor, because the EdgeNGram created m, mo, mot, moto and motor, respectively, and it matches. - When searching for mot, however (i.e. pressing enter when seeing the autosuggestions), it doesn't find any products. The autosuggest field is not part of the real search, and no product attribute contains mot as a word. One obvious solution would be to incorporate the autosuggest field into the real search, however, this adds many tokens to the index that aren't really part of the products indexed and makes for strange search results, for example when an NGram is also a word, but the record itself does contain the search term only as part of a word. Are there clever solutions to this problem?
Best practice: Autosuggest/autocomplete vs. real search
We're using Solr as a backend for an ECommerce site/system. The Solr index stores products with selected attributes, as well as a dedicated field for autocomplete suggestions (Done via AJAX request when typing in the search box without pressing return). The autosuggest field is supplied by copyField directives from certain select product attribute fields (description and/or name mostly). It uses EdgeNGramFilterFactory to complete words not yet typed completely, and it works quite well. However, we come across an issue with a disconnect between the autosuggest results and results of a normal search, that is, a query over the full fields of the product. Let's say there are products that are called motor. - When autosuggesting, typing mot autosuggests all products with motor, because the EdgeNGram created m, mo, mot, moto and motor, respectively, and it matches. - When searching for mot, however (i.e. pressing enter when seeing the autosuggestions), it doesn't find any products. The autosuggest field is not part of the real search, and no product attribute contains mot as a word. One obvious solution would be to incorporate the autosuggest field into the real search, however, this adds many tokens to the index that aren't really part of the products indexed and makes for strange search results, for example when an NGram is also a word, but the record itself does contain the search term only as part of a word. Are there clever solutions to this problem?
Exact matches are not coming on Top for autocomplete search results.
Hi,
I am trying to get the exact search term coming at top in Solr search
results, but solr is not returning the exact matching records on top,
instead exact matching terms are coming somewhere down after few records.
For example :
I am searching for term New York World, and I want the New York World to
come on top of solr search results, but solr is returning results as ,
New York World Journal
New York World Telegram
New York World
*Search query used : *
http://localhost:8981/typeahead/suggest/?q=new+york+world
*schema.xml *
fieldType name=typeahead class=solr.TextField
analyzer type=index
tokenizer class=solr.WhitespaceTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.SynonymFilterFactory synonyms=synonyms.txt
ignoreCase=true expand=true/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.EdgeNGramFilterFactory maxGramSize=100
minGramSize=1/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
analyzer type=query
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.PatternReplaceFilterFactory pattern=^(.{20})(.*)?
replacement=$1 replace=all/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
/fieldType
field name=name_something type=typeahead indexed=true stored=false
multiValued=true/
*solrconfig.xml*
requestHandler name=typeahead class=solr.SearchHandler
lst name=defaults
str name=wtjson/str
int name=rows10/int
str name=indenttrue/str
str name=dfautosuggest/str
str name=q.opAND/str
str name=fl
name_s,pk_id,city_s,state_s,country_s
/requestHandler
kindly provide your suggestions to achieve this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-matches-are-not-coming-on-Top-for-autocomplete-search-results-tp4163162.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Exact matches are not coming on Top for autocomplete search results.
Hi,
You can add an optional (phrase) clause to boost exact matches. If you are
using (e)dismay
bq=typeahead:New York World^50 would do the trick.
Ahmet
On Tuesday, October 7, 2014 6:55 PM, Shobhit shobhitpal48am...@gmail.com
wrote:
Hi,
I am trying to get the exact search term coming at top in Solr search
results, but solr is not returning the exact matching records on top,
instead exact matching terms are coming somewhere down after few records.
For example :
I am searching for term New York World, and I want the New York World to
come on top of solr search results, but solr is returning results as ,
New York World Journal
New York World Telegram
New York World
*Search query used : *
http://localhost:8981/typeahead/suggest/?q=new+york+world
*schema.xml *
fieldType name=typeahead class=solr.TextField
analyzer type=index
tokenizer class=solr.WhitespaceTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.SynonymFilterFactory synonyms=synonyms.txt
ignoreCase=true expand=true/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.EdgeNGramFilterFactory maxGramSize=100
minGramSize=1/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
analyzer type=query
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.PatternReplaceFilterFactory pattern=^(.{20})(.*)?
replacement=$1 replace=all/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
/fieldType
field name=name_something type=typeahead indexed=true stored=false
multiValued=true/
*solrconfig.xml*
requestHandler name=typeahead class=solr.SearchHandler
lst name=defaults
str name=wtjson/str
int name=rows10/int
str name=indenttrue/str
str name=dfautosuggest/str
str name=q.opAND/str
str name=fl
name_s,pk_id,city_s,state_s,country_s
/requestHandler
kindly provide your suggestions to achieve this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-matches-are-not-coming-on-Top-for-autocomplete-search-results-tp4163162.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Exact matches are not coming on Top for autocomplete search results.
bq: bq=typeahead:New York World^50 would do the trick.
I don't think so. All the examples have that phrase in them, so the
boost query would apply to all.
But Shobhit can do something similar with a copyField to a field that,
say, was a keyword tokenizer followed by a lower case filter and put a
very high boost on _that_ instead...
Best,
Erick
On Tue, Oct 7, 2014 at 12:22 PM, Ahmet Arslan iori...@yahoo.com.invalid wrote:
Hi,
You can add an optional (phrase) clause to boost exact matches. If you are
using (e)dismay
bq=typeahead:New York World^50 would do the trick.
Ahmet
On Tuesday, October 7, 2014 6:55 PM, Shobhit shobhitpal48am...@gmail.com
wrote:
Hi,
I am trying to get the exact search term coming at top in Solr search
results, but solr is not returning the exact matching records on top,
instead exact matching terms are coming somewhere down after few records.
For example :
I am searching for term New York World, and I want the New York World to
come on top of solr search results, but solr is returning results as ,
New York World Journal
New York World Telegram
New York World
*Search query used : *
http://localhost:8981/typeahead/suggest/?q=new+york+world
*schema.xml *
fieldType name=typeahead class=solr.TextField
analyzer type=index
tokenizer class=solr.WhitespaceTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.SynonymFilterFactory synonyms=synonyms.txt
ignoreCase=true expand=true/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.EdgeNGramFilterFactory maxGramSize=100
minGramSize=1/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
analyzer type=query
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.PatternReplaceFilterFactory pattern=^(.{20})(.*)?
replacement=$1 replace=all/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
/fieldType
field name=name_something type=typeahead indexed=true stored=false
multiValued=true/
*solrconfig.xml*
requestHandler name=typeahead class=solr.SearchHandler
lst name=defaults
str name=wtjson/str
int name=rows10/int
str name=indenttrue/str
str name=dfautosuggest/str
str name=q.opAND/str
str name=fl
name_s,pk_id,city_s,state_s,country_s
/requestHandler
kindly provide your suggestions to achieve this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-matches-are-not-coming-on-Top-for-autocomplete-search-results-tp4163162.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Exact matches are not coming on Top for autocomplete search results.
Hi Erick,
Yup you are correct. Sorry, I missed that all examples have that phrase.
Ahmet
On Wednesday, October 8, 2014 6:35 AM, Erick Erickson erickerick...@gmail.com
wrote:
bq: bq=typeahead:New York World^50 would do the trick.
I don't think so. All the examples have that phrase in them, so the
boost query would apply to all.
But Shobhit can do something similar with a copyField to a field that,
say, was a keyword tokenizer followed by a lower case filter and put a
very high boost on _that_ instead...
Best,
Erick
On Tue, Oct 7, 2014 at 12:22 PM, Ahmet Arslan iori...@yahoo.com.invalid wrote:
Hi,
You can add an optional (phrase) clause to boost exact matches. If you are
using (e)dismay
bq=typeahead:New York World^50 would do the trick.
Ahmet
On Tuesday, October 7, 2014 6:55 PM, Shobhit shobhitpal48am...@gmail.com
wrote:
Hi,
I am trying to get the exact search term coming at top in Solr search
results, but solr is not returning the exact matching records on top,
instead exact matching terms are coming somewhere down after few records.
For example :
I am searching for term New York World, and I want the New York World to
come on top of solr search results, but solr is returning results as ,
New York World Journal
New York World Telegram
New York World
*Search query used : *
http://localhost:8981/typeahead/suggest/?q=new+york+world
*schema.xml *
fieldType name=typeahead class=solr.TextField
analyzer type=index
tokenizer class=solr.WhitespaceTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.SynonymFilterFactory synonyms=synonyms.txt
ignoreCase=true expand=true/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.EdgeNGramFilterFactory maxGramSize=100
minGramSize=1/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
analyzer type=query
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ISOLatin1AccentFilterFactory/
filter class=solr.PatternReplaceFilterFactory pattern=^(.{20})(.*)?
replacement=$1 replace=all/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
/fieldType
field name=name_something type=typeahead indexed=true stored=false
multiValued=true/
*solrconfig.xml*
requestHandler name=typeahead class=solr.SearchHandler
lst name=defaults
str name=wtjson/str
int name=rows10/int
str name=indenttrue/str
str name=dfautosuggest/str
str name=q.opAND/str
str name=fl
name_s,pk_id,city_s,state_s,country_s
/requestHandler
kindly provide your suggestions to achieve this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Exact-matches-are-not-coming-on-Top-for-autocomplete-search-results-tp4163162.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Autocomplete with Case-insensitive feature
What worked for me was tweaking a code from velocity file, head.vm, I changed
'terms.prefix': function() { return $(#q).val().toLowerCase();}, which
solved my issue as I am using terms component for suggestions.
Dmitry Kan-2 wrote
what kind of suggester are you using? Does its index get rebuilt when you
reindex your data?
From the analysis page at least I see, that you get a hit on Game, which
is
lowercased to game.
On Thu, Apr 17, 2014 at 10:55 AM, Sunayana lt;
sunayana.02@
gt; wrote:
1.My field definition:
fieldType name=text_auto class=solr.TextField
positionIncrementGap=100
analyzer type=index
tokenizer class=solr.StandardTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.ShingleFilterFactory
minShingleSize=2
maxShingleSize=4
outputUnigrams=true
outputUnigramsIfNoShingles=true/
/analyzer
analyzer type=query
tokenizer class=solr.StandardTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
/analyzer
/fieldType
2.On analysis page, it shows me the lowercased word,for both index as
well
as query analyzers.Attaching a screenshot. Is there any other step that I
am
mising out?
lt;http://lucene.472066.n3.nabble.com/file/n4131663/analysis.pnggt;
Dmitry Kan-2 wrote
Could you show the updated field definition?
Does analysis page show sensible output for your query on
indexing/querying
sides?
On Wed, Apr 16, 2014 at 5:52 PM, Sunayana lt;
sunayana.02@
gt; wrote:
Thanks for replying,
1.Yes,I re-indexed data after the changes.
2.Changing to STF, did not help..
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Dmitry
Blog: http://dmitrykan.blogspot.com
Twitter: http://twitter.com/dmitrykan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131663.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
Dmitry
Blog: http://dmitrykan.blogspot.com
Twitter: http://twitter.com/dmitrykan
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4135560.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Autocomplete with Case-insensitive feature
what kind of suggester are you using? Does its index get rebuilt when you reindex your data? From the analysis page at least I see, that you get a hit on Game, which is lowercased to game. On Thu, Apr 17, 2014 at 10:55 AM, Sunayana sunayana...@wipro.com wrote: 1.My field definition: fieldType name=text_auto class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ /analyzer /fieldType 2.On analysis page, it shows me the lowercased word,for both index as well as query analyzers.Attaching a screenshot. Is there any other step that I am mising out? http://lucene.472066.n3.nabble.com/file/n4131663/analysis.png Dmitry Kan-2 wrote Could you show the updated field definition? Does analysis page show sensible output for your query on indexing/querying sides? On Wed, Apr 16, 2014 at 5:52 PM, Sunayana lt; sunayana.02@ gt; wrote: Thanks for replying, 1.Yes,I re-indexed data after the changes. 2.Changing to STF, did not help.. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131663.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan
Re: Autocomplete with Case-insensitive feature
1.My field definition: fieldType name=text_auto class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ /analyzer /fieldType 2.On analysis page, it shows me the lowercased word,for both index as well as query analyzers.Attaching a screenshot. Is there any other step that I am mising out? http://lucene.472066.n3.nabble.com/file/n4131663/analysis.png Dmitry Kan-2 wrote Could you show the updated field definition? Does analysis page show sensible output for your query on indexing/querying sides? On Wed, Apr 16, 2014 at 5:52 PM, Sunayana lt; sunayana.02@ gt; wrote: Thanks for replying, 1.Yes,I re-indexed data after the changes. 2.Changing to STF, did not help.. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131663.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Autocomplete with Case-insensitive feature
1. did you re-index after changing schema? 2. Why do use KeywordTokenizerFactory and not StandardTokenizerFactory? KTF treats entire field contents as one token. Does it do what you really want? [1] 3. If you'd use STF, TrimFilterFactory would be obsolete, as tokenization has been done already. [1] http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.KeywordTokenizerFactory On Tue, Apr 15, 2014 at 12:24 PM, Sunayana sunayana...@wipro.com wrote: Hi, Did u mean changing field type as fieldType name=text_auto class=solr.TextField positionIncrementGap=100 indexed=true stored=false multiValued=true analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.KeywordTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.TrimFilterFactory / /analyzer /fieldType This did not work out for me. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131198.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan
Re: Autocomplete with Case-insensitive feature
Thanks for replying, 1.Yes,I re-indexed data after the changes. 2.Changing to STF, did not help.. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Autocomplete with Case-insensitive feature
Could you show the updated field definition? Does analysis page show sensible output for your query on indexing/querying sides? On Wed, Apr 16, 2014 at 5:52 PM, Sunayana sunayana...@wipro.com wrote: Thanks for replying, 1.Yes,I re-indexed data after the changes. 2.Changing to STF, did not help.. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131499.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan
Autocomplete with Case-insensitive feature
Hi All, I have been trying out this autocomplete feature in Solr4.7.1 using Suggester.I have configured it to display phrase suggestions also.Problem is If I type game I get suggestions as game or phrases containing game. But If I type Game *no suggestion is displayed at all*.How can I get suggestions case-insensitive? I have defined in schema.xml fields like this: field name=name_autocomplete type=text_auto indexed=true stored=true multiValued=true / copyField source=name dest=name_autocomplete / fieldType name=text_auto class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.KeywordTokenizerFactory/ filter class=solr.TrimFilterFactory / /analyzer /fieldType -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: Autocomplete with Case-insensitive feature
Hi, Configure LowerCaseFilterFactory into the query side of your type config. Dmitry On Tue, Apr 15, 2014 at 10:50 AM, Sunayana sunayana...@wipro.com wrote: Hi All, I have been trying out this autocomplete feature in Solr4.7.1 using Suggester.I have configured it to display phrase suggestions also.Problem is If I type game I get suggestions as game or phrases containing game. But If I type Game *no suggestion is displayed at all*.How can I get suggestions case-insensitive? I have defined in schema.xml fields like this: field name=name_autocomplete type=text_auto indexed=true stored=true multiValued=true / copyField source=name dest=name_autocomplete / fieldType name=text_auto class=solr.TextField positionIncrementGap=100 analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.KeywordTokenizerFactory/ filter class=solr.TrimFilterFactory / /analyzer /fieldType -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182.html Sent from the Solr - User mailing list archive at Nabble.com. -- Dmitry Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan
Re: Autocomplete with Case-insensitive feature
Hi, Did u mean changing field type as fieldType name=text_auto class=solr.TextField positionIncrementGap=100 indexed=true stored=false multiValued=true analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory minShingleSize=2 maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=true/ /analyzer analyzer type=query tokenizer class=solr.KeywordTokenizerFactory/ filter class=solr.LowerCaseFilterFactory/ filter class=solr.TrimFilterFactory / /analyzer /fieldType This did not work out for me. -- View this message in context: http://lucene.472066.n3.nabble.com/Autocomplete-with-Case-insensitive-feature-tp4131182p4131198.html Sent from the Solr - User mailing list archive at Nabble.com.
Solr 4.7 Autocomplete
Hi, I am new to solr, Is it possible to accomplish autocomplete through ( Terms or Suggest or Facet ) over a date range. I need to have a autocomplete over a field between a date range from another field. Thanks newbie
Re: Solr 4.7 Autocomplete
Hi, What do you mean by 'date range' ? Faceting component respects q or fq parameters, so if you set fq=date:[somedate TO otherdate] yes faceting values will change. facet.prefix can be used for auto complete. On Thursday, February 27, 2014 5:03 PM, Bala Iyer grb...@yahoo.com wrote: Hi, I am new to solr, Is it possible to accomplish autocomplete through ( Terms or Suggest or Facet ) over a date range. I need to have a autocomplete over a field between a date range from another field. Thanks newbie
Re: Solr 4.7 Autocomplete
Thanks for the quick response, I have configured suggest and its working great but its searching all the documents. From my field definition: I need to search between specific timestamp and by username fields for autocomplete by field content/content_autosuggest. I need to autocomplete word google between 2013-01-01T00:00:00Z and 2013-12-31T23:59:59Z for username John when i type goo IS IT POSSIBLE? == Schema.xml fieldType class=solr.TextField name=text_auto analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt / filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=false / /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt / filter class=solr.LowerCaseFilterFactory/ filter class=solr.StandardFilterFactory/ filter class=solr.RemoveDuplicatesTokenFilterFactory/ /analyzer /fieldType field name=username type=string indexed=true stored=true multiValued=true omitNorms=true termVectors=true / field name=timestamp type=date indexed=true stored=true multiValued=true omitNorms=true termVectors=true / field name=content_autosuggest type=text_auto indexed=true stored=true multiValued=true/ copyField source=content dest=content_autosuggest/ copyField source=id dest=content_autosuggest/ copyField source=username dest=content_autosuggest/ copyField source=timestamp dest=content_autosuggest/ solrconfig.xml searchComponent class=solr.SpellCheckComponent name=suggest lst name=spellchecker str name=namesuggest/str str name=classnameorg.apache.solr.spelling.suggest.Suggester/str str name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookup/str str name=fieldcontent_autosuggest/str !-- the indexed field to derive suggestions from -- str name=buildOnCommittrue/str /lst str name=queryAnalyzerFieldTypetext_auto/str /searchComponent requestHandler class=org.apache.solr.handler.component.SearchHandler name=/suggest lst name=defaults str name=dfcontent_autosuggest/str str name=spellchecktrue/str str name=spellcheck.dictionarysuggest/str str name=spellcheck.onlyMorePopulartrue/str str name=spellcheck.count25/str str name=spellcheck.collatetrue/str /lst arr name=components strsuggest/str /arr /requestHandler = i tried http://localhost:8983/solr/collection1/select?facet=truefq=timestamp:[2013-01-01T00:00:00Z%20TO%202013-12-02T00:00:00Z]facet.prefix=google No result result name=response numFound=0 start=0/ BUT http://localhost:8983/solr/collection1/select?q=google i get result name=response numFound=4918 start=0 doc str name=id103154/str arr name=content_autosuggest str103154/str strJohn/str str2013-09-10T08:02:28Z/str strGoogle Chrome/str /arr arr name=username strJohn/str /arr arr name=timestamp date2013-09-10T08:02:28Z/date /arr arr name=content strGoogle Chrome/str /arr long name=_version_1461215424741900288/long /doc Thanks On Thursday, February 27, 2014 1:08 PM, Ahmet Arslan iori...@yahoo.com wrote: Hi, What do you mean by 'date range' ? Faceting component respects q or fq parameters, so if you set fq=date:[somedate TO otherdate] yes faceting values will change. facet.prefix can be used for auto complete. On Thursday, February 27, 2014 5:03 PM, Bala Iyer grb...@yahoo.com wrote: Hi, I am new to solr, Is it possible to accomplish autocomplete through ( Terms or Suggest or Facet ) over a date range. I need to have a autocomplete over a field between a date range from another field. Thanks newbie
Re: Solr 4.7 Autocomplete
Hi, http://localhost:8983/solr/collection1/select?facet=truefq=timestamp:[2013-01-01T00:00:00Z%20TO%202013-12-02T00:00:00Z]facet.prefix=google You url misses these parameters : q=*:* facet.field=content_autosuggest And if you are getting numFound=0 because of your filter query, we cannot generate any suggestion. Try relaxing your filter query first. Ahmet On Friday, February 28, 2014 12:04 AM, Bala Iyer grb...@yahoo.com wrote: Thanks for the quick response, I have configured suggest and its working great but its searching all the documents. From my field definition: I need to search between specific timestamp and by username fields for autocomplete by field content/content_autosuggest. I need to autocomplete word google between 2013-01-01T00:00:00Z and 2013-12-31T23:59:59Z for username John when i type goo IS IT POSSIBLE? == Schema.xml fieldType class=solr.TextField name=text_auto analyzer type=index tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt / filter class=solr.LowerCaseFilterFactory/ filter class=solr.ShingleFilterFactory maxShingleSize=4 outputUnigrams=true outputUnigramsIfNoShingles=false / /analyzer analyzer type=query tokenizer class=solr.StandardTokenizerFactory/ filter class=solr.StopFilterFactory ignoreCase=true words=stopwords.txt / filter class=solr.LowerCaseFilterFactory/ filter class=solr.StandardFilterFactory/ filter class=solr.RemoveDuplicatesTokenFilterFactory/ /analyzer /fieldType field name=username type=string indexed=true stored=true multiValued=true omitNorms=true termVectors=true / field name=timestamp type=date indexed=true stored=true multiValued=true omitNorms=true termVectors=true / field name=content_autosuggest type=text_auto indexed=true stored=true multiValued=true/ copyField source=content dest=content_autosuggest/ copyField source=id dest=content_autosuggest/ copyField source=username dest=content_autosuggest/ copyField source=timestamp dest=content_autosuggest/ solrconfig.xml searchComponent class=solr.SpellCheckComponent name=suggest lst name=spellchecker str name=namesuggest/str str name=classnameorg.apache.solr.spelling.suggest.Suggester/str str name=lookupImplorg.apache.solr.spelling.suggest.tst.TSTLookup/str str name=fieldcontent_autosuggest/str !-- the indexed field to derive suggestions from -- str name=buildOnCommittrue/str /lst str name=queryAnalyzerFieldTypetext_auto/str /searchComponent requestHandler class=org.apache.solr.handler.component.SearchHandler name=/suggest lst name=defaults str name=dfcontent_autosuggest/str str name=spellchecktrue/str str name=spellcheck.dictionarysuggest/str str name=spellcheck.onlyMorePopulartrue/str str name=spellcheck.count25/str str name=spellcheck.collatetrue/str /lst arr name=components strsuggest/str /arr /requestHandler = i tried http://localhost:8983/solr/collection1/select?facet=truefq=timestamp:[2013-01-01T00:00:00Z%20TO%202013-12-02T00:00:00Z]facet.prefix=google No result result name=response numFound=0 start=0/ BUT http://localhost:8983/solr/collection1/select?q=google i get result name=response numFound=4918 start=0 doc str name=id103154/str arr name=content_autosuggest str103154/str strJohn/str str2013-09-10T08:02:28Z/str strGoogle Chrome/str /arr arr name=username strJohn/str /arr arr name=timestamp date2013-09-10T08:02:28Z/date /arr arr name=content strGoogle Chrome/str /arr long name=_version_1461215424741900288/long /doc Thanks On Thursday, February 27, 2014 1:08 PM, Ahmet Arslan iori...@yahoo.com wrote: Hi, What do you mean by 'date range' ? Faceting component respects q or fq parameters, so if you set fq=date:[somedate TO otherdate] yes faceting values will change. facet.prefix can be used for auto complete. On Thursday, February 27, 2014 5:03 PM, Bala Iyer grb...@yahoo.com wrote: Hi, I am new to solr, Is it possible to accomplish autocomplete through ( Terms or Suggest or Facet ) over a date range. I need to have a autocomplete over a field between a date range from another field. Thanks newbie
Re: Solr Autocomplete with did you means functionality handle misspell word like google
It's really simple indeed. Solr provide the SpellCheck[1] feature that allow you to do this. You have only to configure the RequestHandler and the Search Component. And of course develop a simple ui ( you can find an example in the velocity response handler Solritas[2] . Cheers [1] https://cwiki.apache.org/confluence/display/solr/Spell+Checking [2] https://cwiki.apache.org/confluence/display/solr/Velocity+Search+UI 2013/9/27 Otis Gospodnetic otis.gospodne...@gmail.com Hi, Not sure if Solr suggester can do this (can it, anyone?), but... shameless plug... I know http://sematext.com/products/autocomplete/index.html can do that. Otis -- Solr ElasticSearch Support -- http://sematext.com/ Performance Monitoring -- http://sematext.com/spm On Thu, Sep 26, 2013 at 8:26 AM, Suneel Pandey pandey.sun...@gmail.com wrote: http://lucene.472066.n3.nabble.com/file/n4092127/autocomplete.png Hi, I have implemented auto complete it's working file but, I want to implement autosuggestion like google (see above screen) . when someone typing misspell words suggestion should be show e.g: cmputer = computer. Please help me. - Regards, Suneel Pandey Sr. Software Developer -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-Autocomplete-with-did-you-means-functionality-handle-misspell-word-like-google-tp4092127.html Sent from the Solr - User mailing list archive at Nabble.com. -- -- Benedetti Alessandro Visiting card : http://about.me/alessandro_benedetti Tyger, tyger burning bright In the forests of the night, What immortal hand or eye Could frame thy fearful symmetry? William Blake - Songs of Experience -1794 England
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I forgot to mention you could check the boost section on the configuration file
of the core to see how your suggestions will be ranked, basically the boost
factor for each field allows you to decide which suggestion do you like to come
first, perhaps in your app you could keep track of how much a suggestion given
to a user is actually used as the query and boost this suggestions as is more
likely to become a query for the user; thinking a little ahead this could
improve your user experience and additionally low the load on your server,
because if a suggestion given to a high number of users become a query, this
query should already be in the cache. This are just thoughts but I hope could
be useful to you.
Regards,
- Mensaje original -
De: Ing. Jorge Luis Betancourt Gonzalez jlbetanco...@uci.cu
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 19:44:28
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Actually I don't use that field, it could be used to do some form of basic
collaborative filtering, so you could use a high value for items in your
collection that you want to come first, but in my case this was not a
requirement and I don't use it at all.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 16:19:40
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I am not sure about the value to use for the option popularity. Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Jueves, 26 de Septiembre 2013 9:10:49
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
solved.
On Thu, Sep 26, 2013 at 1:50 PM, JMill apprentice...@googlemail.com
wrote:
I managed to get rid of the query error by playing jquery file in the
velocity folder and adding line: script type=text/javascript
src=#{url_for_solr}/admin/file?file=/velocity/jquery.min.jscontentType=text/javascript/script.
That has not solved the issues the console is showing a new error -
[13:42:55.181] TypeError: $.browser is undefined @
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.jscontentType=text/javascript:90
.
Any ideas?
On Thu, Sep 26, 2013 at 1:12 PM, JMill apprentice...@googlemail.com
wrote:
Do you know the directory the #{url_root} in script
type=text/javascript src=#{url_root}/js/lib/
jquery-1.7.2.min.js/script points too? and same for
#{url_for_solr} script type=text/javascript
src=#{url_for_solr}/js/lib/jquery-1.7.2.min.js/script
On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Try quering the core where the data has been imported, something like:
http://localhost:8983/solr/suggestions/select?q=uc
In the previous URL suggestions is the name I give to the core, so this
should change, if you get results, then the problem could be the jquery
dependency. I don't remember doing any change, as far as I know that js
file is bundled with solr (at leat in 3.x) version perhaps you could
change
it the correct jquery version on solr 4.4, if you go into the admin
panel
(in solr 3.6):
http://localhost:8983/solr/admin/schema.jsp
And inspect the loaded code, the required file (jquery-1.4.2.min.js)
gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
recent version.
Perhaps you could change that part to something like:
script type=text/javascript
src=#{url_root}/js/lib/jquery-1.7.2.min.js/script
Which is used at least on a solr 4.1 that I have laying aroud here
somewhere.
In any case you can test the suggestions using the URL that I suggest
on
the top of this mail, in that case you should be able to see the
possible
results, of course in a less fancy way.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
Could it be the jquery library that is the problem? I opened up
solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
to
the jquery library but I can't seem to find the directory referenced,
line: script type=text/javascript
src=#{url_for_solr}/admin/jquery-1.4.3.min.js. Do you know where
#{url_for_solr} points to?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
III Escuela Internacional de
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I am not sure about the value to use for the option popularity. Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Jueves, 26 de Septiembre 2013 9:10:49
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
solved.
On Thu, Sep 26, 2013 at 1:50 PM, JMill apprentice...@googlemail.com
wrote:
I managed to get rid of the query error by playing jquery file in the
velocity folder and adding line: script type=text/javascript
src=#{url_for_solr}/admin/file?file=/velocity/jquery.min.jscontentType=text/javascript/script.
That has not solved the issues the console is showing a new error -
[13:42:55.181] TypeError: $.browser is undefined @
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.jscontentType=text/javascript:90
.
Any ideas?
On Thu, Sep 26, 2013 at 1:12 PM, JMill apprentice...@googlemail.com
wrote:
Do you know the directory the #{url_root} in script
type=text/javascript src=#{url_root}/js/lib/
jquery-1.7.2.min.js/script points too? and same for
#{url_for_solr} script type=text/javascript
src=#{url_for_solr}/js/lib/jquery-1.7.2.min.js/script
On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Try quering the core where the data has been imported, something like:
http://localhost:8983/solr/suggestions/select?q=uc
In the previous URL suggestions is the name I give to the core, so this
should change, if you get results, then the problem could be the jquery
dependency. I don't remember doing any change, as far as I know that js
file is bundled with solr (at leat in 3.x) version perhaps you could
change
it the correct jquery version on solr 4.4, if you go into the admin
panel
(in solr 3.6):
http://localhost:8983/solr/admin/schema.jsp
And inspect the loaded code, the required file (jquery-1.4.2.min.js)
gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
recent version.
Perhaps you could change that part to something like:
script type=text/javascript
src=#{url_root}/js/lib/jquery-1.7.2.min.js/script
Which is used at least on a solr 4.1 that I have laying aroud here
somewhere.
In any case you can test the suggestions using the URL that I suggest
on
the top of this mail, in that case you should be able to see the
possible
results, of course in a less fancy way.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
Could it be the jquery library that is the problem? I opened up
solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
to
the jquery library but I can't seem to find the directory referenced,
line: script type=text/javascript
src=#{url_for_solr}/admin/jquery-1.4.3.min.js. Do you know where
#{url_for_solr} points to?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
Re: Implementing Solr Suggester for Autocomplete (multiple columns)
Actually I don't use that field, it could be used to do some form of basic
collaborative filtering, so you could use a high value for items in your
collection that you want to come first, but in my case this was not a
requirement and I don't use it at all.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Viernes, 27 de Septiembre 2013 16:19:40
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple columns)
I am not sure about the value to use for the option popularity. Is there
a method or do you just go with some arbitrary number?
On Thursday, September 26, 2013, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Great!! I haven't see your message yet, perhaps you could create a PR to
that Github repository, son it will be in sync with current versions of
Solr.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Jueves, 26 de Septiembre 2013 9:10:49
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
solved.
On Thu, Sep 26, 2013 at 1:50 PM, JMill apprentice...@googlemail.com
wrote:
I managed to get rid of the query error by playing jquery file in the
velocity folder and adding line: script type=text/javascript
src=#{url_for_solr}/admin/file?file=/velocity/jquery.min.jscontentType=text/javascript/script.
That has not solved the issues the console is showing a new error -
[13:42:55.181] TypeError: $.browser is undefined @
http://localhost:8983/solr/ac/admin/file?file=/velocity/jquery.autocomplete.jscontentType=text/javascript:90
.
Any ideas?
On Thu, Sep 26, 2013 at 1:12 PM, JMill apprentice...@googlemail.com
wrote:
Do you know the directory the #{url_root} in script
type=text/javascript src=#{url_root}/js/lib/
jquery-1.7.2.min.js/script points too? and same for
#{url_for_solr} script type=text/javascript
src=#{url_for_solr}/js/lib/jquery-1.7.2.min.js/script
On Wed, Sep 25, 2013 at 7:33 PM, Ing. Jorge Luis Betancourt Gonzalez
jlbetanco...@uci.cu wrote:
Try quering the core where the data has been imported, something like:
http://localhost:8983/solr/suggestions/select?q=uc
In the previous URL suggestions is the name I give to the core, so this
should change, if you get results, then the problem could be the jquery
dependency. I don't remember doing any change, as far as I know that js
file is bundled with solr (at leat in 3.x) version perhaps you could
change
it the correct jquery version on solr 4.4, if you go into the admin
panel
(in solr 3.6):
http://localhost:8983/solr/admin/schema.jsp
And inspect the loaded code, the required file (jquery-1.4.2.min.js)
gets loaded in solr 4.4 it should load a similar file, but perhaps a
more
recent version.
Perhaps you could change that part to something like:
script type=text/javascript
src=#{url_root}/js/lib/jquery-1.7.2.min.js/script
Which is used at least on a solr 4.1 that I have laying aroud here
somewhere.
In any case you can test the suggestions using the URL that I suggest
on
the top of this mail, in that case you should be able to see the
possible
results, of course in a less fancy way.
- Mensaje original -
De: JMill apprentice...@googlemail.com
Para: solr-user@lucene.apache.org
Enviados: Miércoles, 25 de Septiembre 2013 13:59:32
Asunto: Re: Implementing Solr Suggester for Autocomplete (multiple
columns)
Could it be the jquery library that is the problem? I opened up
solr-home/ac/conf/velocity/head.vm with an editor and I see a reference
to
the jquery library but I can't seem to find the directory referenced,
line: script type=text/javascript
src=#{url_for_solr}/admin/jquery-1.4.3.min.js. Do you know where
#{url_for_solr} points to?
On Wednesday, September 25, 2013, Ing. Jorge Luis Betancourt Gonzalez
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del
2014. Ver www.uci.cu
III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del
2014. Ver www.uci.cu
