You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by mechravi25 <me...@yahoo.co.in> on 2011/11/16 15:17:37 UTC
Problems with AutoSuggest feature(Terms Components)
Hi,
When i search for a data i noticed two things
1.) I noticed that *terms.regex=.*&* in the logs which does a blank search
on terms because of the query time is more. Is there anyway to overcome
this. My actual query should go like the first one bolded but instead of
that it happens like in the second case(the 2nd text highlighted in bold)
2.) Also I noticed that *terms.limit=-1* which is very expensive as it asks
solr to return all the terms back. It should be set to 10 or 20 at most.
Please provide some suggestions to set the same.
Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
INFO: [db] webapp=/solr path=/terms
params={*terms.regex=ABC\+CCC\+lll*\+data.*&terms.regex.flag=case_insensitive&terms.fl=nameFacet}
status=0 QTime=935
Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
INFO: [core2] webapp=/solr path=/terms
params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=ABC\+CCC\+lll\+data.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
status=0 QTime=842
Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
INFO: [db] webapp=/solr path=/terms
params={terms.regex=ABC\+CCC\+lll\+data.*&terms.regex.flag=case_insensitive&terms.fl=nameFacet}
status=0 QTime=927
Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
INFO: [core3] webapp=/solr path=/terms
params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
status=0 QTime=115
Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
INFO: [core1] webapp=/solr path=/terms
params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&*terms.regex=.**&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
status=0 QTime=106767
Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
INFO: [core4] webapp=/solr path=/terms
params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
status=0 QTime=106766
Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
--
View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-AutoSuggest-feature-Terms-Components-tp3512734p3512734.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with AutoSuggest feature(Terms Components)
Posted by Erick Erickson <er...@gmail.com>.
I'll have to defer that to one of the sharding experts.....
Best
Erick
On Tue, Nov 22, 2011 at 1:28 PM, mechravi25 <me...@yahoo.co.in> wrote:
> Hi Erick,
>
> Thanks for your reply. I would know all the options that can be given under
> the defaults section and how they can be overridden. is there any
> documentation available in solr forum. Cos we tried searching and wasn't
> able to succeed.
>
> My Exact scenario is that, I have one master core which has many underlying
> shards core(Disturbed architecture). I want the terms.limit should be
> defaulted to 10 in the underlying shards cores. When i hit the master core,
> it will in-turn hit the underlying shard cores. At this point of time, the
> terms.limit which has been passed to the master core has to passed to these
> underlying shard cores overriding the default value set. Can you please
> suggest the definition of the terms component for the underlying shard
> cores.
>
> Regards,
> Sivaganesh
>
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-AutoSuggest-feature-Terms-Components-tp3512734p3528597.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Re: Problems with AutoSuggest feature(Terms Components)
Posted by mechravi25 <me...@yahoo.co.in>.
Hi Erick,
Thanks for your reply. I would know all the options that can be given under
the defaults section and how they can be overridden. is there any
documentation available in solr forum. Cos we tried searching and wasn't
able to succeed.
My Exact scenario is that, I have one master core which has many underlying
shards core(Disturbed architecture). I want the terms.limit should be
defaulted to 10 in the underlying shards cores. When i hit the master core,
it will in-turn hit the underlying shard cores. At this point of time, the
terms.limit which has been passed to the master core has to passed to these
underlying shard cores overriding the default value set. Can you please
suggest the definition of the terms component for the underlying shard
cores.
Regards,
Sivaganesh
--
View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-AutoSuggest-feature-Terms-Components-tp3512734p3528597.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Problems with AutoSuggest feature(Terms Components)
Posted by Erick Erickson <er...@gmail.com>.
TermsComponent only reacts to what you send it. How are these requests
getting to the TermsComponent? That's where you should look.
As far as terms.limit, your requesthandler for TermsComponent in
solrconfig.xml has a <defaults> section and you can set whatever
you want in there and then override it as you choose if you
sometimes want other values in there.
Best
Erick
On Wed, Nov 16, 2011 at 9:17 AM, mechravi25 <me...@yahoo.co.in> wrote:
> Hi,
>
> When i search for a data i noticed two things
>
> 1.) I noticed that *terms.regex=.*&* in the logs which does a blank search
> on terms because of the query time is more. Is there anyway to overcome
> this. My actual query should go like the first one bolded but instead of
> that it happens like in the second case(the 2nd text highlighted in bold)
>
> 2.) Also I noticed that *terms.limit=-1* which is very expensive as it asks
> solr to return all the terms back. It should be set to 10 or 20 at most.
> Please provide some suggestions to set the same.
>
>
>
> Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
> INFO: [db] webapp=/solr path=/terms
> params={*terms.regex=ABC\+CCC\+lll*\+data.*&terms.regex.flag=case_insensitive&terms.fl=nameFacet}
> status=0 QTime=935
> Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
> INFO: [core2] webapp=/solr path=/terms
> params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=ABC\+CCC\+lll\+data.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
> status=0 QTime=842
> Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
> INFO: [db] webapp=/solr path=/terms
> params={terms.regex=ABC\+CCC\+lll\+data.*&terms.regex.flag=case_insensitive&terms.fl=nameFacet}
> status=0 QTime=927
> Nov 14, 2011 2:04:08 PM org.apache.solr.core.SolrCore execute
> INFO: [core3] webapp=/solr path=/terms
> params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
> status=0 QTime=115
>
> Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
> INFO: [core1] webapp=/solr path=/terms
> params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&*terms.regex=.**&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
> status=0 QTime=106767
> Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
> INFO: [core4] webapp=/solr path=/terms
> params={terms.regex.flag=case_insensitive&shards.qt=/terms&terms.fl=nameFacet&terms=true&terms.limit=-1&terms.regex=.*&isShard=true&qt=/terms&wt=javabin&terms.sort=index&version=1}
> status=0 QTime=106766
> Nov 14, 2011 2:05:55 PM org.apache.solr.core.SolrCore execute
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/Problems-with-AutoSuggest-feature-Terms-Components-tp3512734p3512734.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>