Re: Non-contigous terms in SuggestComponent
Hi Alfonso, I think we can't escape totally from edismax. I guess we just have to try to optimise the performance. I'm dealing with similar issues at the moment now. Regards, Edwin On 3 March 2016 at 00:14, Alfonso Muñoz-Pomer Fuentes wrote: > Hi Edwin. > > That was what I suspected, but I wanted to confirm. If we go down this > route I’ll do some testing and post the results. > > We’re using 5.1 in production, but I’m testing with 5.4.1. > > The index has 40,891,287 documents and is 3.01 GB, so it’s not big at all. > > Many thanks, > Alfonso > > > On 01/03/2016 06:25, Zheng Lin Edwin Yeo wrote: > >> From what I have experienced, the performance using edismax will be >> slower. >> It may not be that significant if your index size is small, but it will >> get >> more significant as your index size grows. >> >> By the way, which version of Solr are you using? >> >> Regards, >> Edwin >> >> >> On 29 February 2016 at 21:33, Alfonso Muñoz-Pomer Fuentes < >> amu...@ebi.ac.uk> >> wrote: >> >> Hi all. >>> >>> I’ve been reading through the Suggester component in Solr at >>> https://cwiki.apache.org/confluence/display/solr/Suggester. >>> >>> I have a couple of questions regarding it which I haven’t been able to >>> find the answer for in that page or anywhere else. >>> >>> Is there a way to get suggestions from non-contiguous terms using a >>> SuggestComponent? E.g. let’s say we have a document which contains “The >>> quick brown fox” in a text field, can it be configured so that a user can >>> obtain that suggestion by typing “quick fox”? >>> >>> I know I can get this sort of results using edismax queries, so maybe I >>> can set a request handler to do suggestions in this way instead than with >>> SuggestComponent. What are the downsides performance-wise? >>> >>> Thank you in advance. >>> >>> -- >>> Alfonso Muñoz-Pomer Fuentes >>> Software Engineer @ Expression Atlas Team >>> European Bioinformatics Institute (EMBL-EBI) >>> European Molecular Biology Laboratory >>> Tel:+ 44 (0) 1223 49 2633 >>> Skype: amunozpomer >>> >>> >> > -- > Alfonso Muñoz-Pomer Fuentes > Software Engineer @ Expression Atlas Team > European Bioinformatics Institute (EMBL-EBI) > European Molecular Biology Laboratory > Tel:+ 44 (0) 1223 49 2633 > Skype: amunozpomer >
Re: Non-contigous terms in SuggestComponent
Hi Edwin. That was what I suspected, but I wanted to confirm. If we go down this route I’ll do some testing and post the results. We’re using 5.1 in production, but I’m testing with 5.4.1. The index has 40,891,287 documents and is 3.01 GB, so it’s not big at all. Many thanks, Alfonso On 01/03/2016 06:25, Zheng Lin Edwin Yeo wrote: From what I have experienced, the performance using edismax will be slower. It may not be that significant if your index size is small, but it will get more significant as your index size grows. By the way, which version of Solr are you using? Regards, Edwin On 29 February 2016 at 21:33, Alfonso Muñoz-Pomer Fuentes wrote: Hi all. I’ve been reading through the Suggester component in Solr at https://cwiki.apache.org/confluence/display/solr/Suggester. I have a couple of questions regarding it which I haven’t been able to find the answer for in that page or anywhere else. Is there a way to get suggestions from non-contiguous terms using a SuggestComponent? E.g. let’s say we have a document which contains “The quick brown fox” in a text field, can it be configured so that a user can obtain that suggestion by typing “quick fox”? I know I can get this sort of results using edismax queries, so maybe I can set a request handler to do suggestions in this way instead than with SuggestComponent. What are the downsides performance-wise? Thank you in advance. -- Alfonso Muñoz-Pomer Fuentes Software Engineer @ Expression Atlas Team European Bioinformatics Institute (EMBL-EBI) European Molecular Biology Laboratory Tel:+ 44 (0) 1223 49 2633 Skype: amunozpomer -- Alfonso Muñoz-Pomer Fuentes Software Engineer @ Expression Atlas Team European Bioinformatics Institute (EMBL-EBI) European Molecular Biology Laboratory Tel:+ 44 (0) 1223 49 2633 Skype: amunozpomer
Re: Non-contigous terms in SuggestComponent
>From what I have experienced, the performance using edismax will be slower. It may not be that significant if your index size is small, but it will get more significant as your index size grows. By the way, which version of Solr are you using? Regards, Edwin On 29 February 2016 at 21:33, Alfonso Muñoz-Pomer Fuentes wrote: > Hi all. > > I’ve been reading through the Suggester component in Solr at > https://cwiki.apache.org/confluence/display/solr/Suggester. > > I have a couple of questions regarding it which I haven’t been able to > find the answer for in that page or anywhere else. > > Is there a way to get suggestions from non-contiguous terms using a > SuggestComponent? E.g. let’s say we have a document which contains “The > quick brown fox” in a text field, can it be configured so that a user can > obtain that suggestion by typing “quick fox”? > > I know I can get this sort of results using edismax queries, so maybe I > can set a request handler to do suggestions in this way instead than with > SuggestComponent. What are the downsides performance-wise? > > Thank you in advance. > > -- > Alfonso Muñoz-Pomer Fuentes > Software Engineer @ Expression Atlas Team > European Bioinformatics Institute (EMBL-EBI) > European Molecular Biology Laboratory > Tel:+ 44 (0) 1223 49 2633 > Skype: amunozpomer >
Non-contigous terms in SuggestComponent
Hi all. I’ve been reading through the Suggester component in Solr at https://cwiki.apache.org/confluence/display/solr/Suggester. I have a couple of questions regarding it which I haven’t been able to find the answer for in that page or anywhere else. Is there a way to get suggestions from non-contiguous terms using a SuggestComponent? E.g. let’s say we have a document which contains “The quick brown fox” in a text field, can it be configured so that a user can obtain that suggestion by typing “quick fox”? I know I can get this sort of results using edismax queries, so maybe I can set a request handler to do suggestions in this way instead than with SuggestComponent. What are the downsides performance-wise? Thank you in advance. -- Alfonso Muñoz-Pomer Fuentes Software Engineer @ Expression Atlas Team European Bioinformatics Institute (EMBL-EBI) European Molecular Biology Laboratory Tel:+ 44 (0) 1223 49 2633 Skype: amunozpomer
