a thorough example for any Solr-user can
>> understand years ago, it'll help you make a decent autocomplete and
>> improve understanding of Lucene and Solr:
>> http://www.cominvent.com/2012/01/25/super-flexible-autocomplete-with-solr/
>>
>> -----Original message---
message-
> > From:Lo Dave
> > Sent: Thursday 23rd July 2015 3:18
> > To: solr-user@lucene.apache.org
> > Subject: RE: Performance of facet contain search in 5.2.1
> >
> > Yes. I am going to provide autocomplete with facet count as rank.i.e.
> when yours inpu
y 2015 3:18
> To: solr-user@lucene.apache.org
> Subject: RE: Performance of facet contain search in 5.2.1
>
> Yes. I am going to provide autocomplete with facet count as rank.i.e. when
> yours input "owe a duty", the system will suggest "xxx owe a duty yyy" wi
Yes. I am going to provide autocomplete with facet count as rank.i.e. when
yours input "owe a duty", the system will suggest "xxx owe a duty yyy" with
highest count.
Thanks.
Dave
> Date: Wed, 22 Jul 2015 14:35:40 +0100
> Subject: Re: Performance of facet cont
the facet field as n-grams? It blows up the index
> but is very fast!
> Markus
>
> -Original message-
> > From:Erick Erickson
> > Sent: Tuesday 21st July 2015 21:36
> > To: solr-user@lucene.apache.org
> > Subject: Re: Performance of facet contain se
Hello - why not index the facet field as n-grams? It blows up the index but is
very fast!
Markus
-Original message-
> From:Erick Erickson
> Sent: Tuesday 21st July 2015 21:36
> To: solr-user@lucene.apache.org
> Subject: Re: Performance of facet contain search in 5.2.1
&g
"contains" has to basically examine each and every term to see if it
matches. Say my
facet.contains=bbb. A matching term could be
aaabbbxyz
or
zzzbbbxyz
So there's no way to _know_ when you've found them all without
examining every last
one. So I'd try to redefine the problem to not require that.
Hi Dave,
generally giving terms in a dictionary, it's much more efficient to run
prefix queries than "contain" queries.
Talking about using docValues, if I remember well when they are loaded in
memory they are skipList, so you can use two operators on them :
- next() that simply gives you ht next
I found that facet contain search take much longer time than facet prefix
search. Do anyone have idea how to make contain search faster?
org.apache.solr.core.SolrCore; [concordance] webapp=/solr path=/select
params={q=sentence:"duty+of+care"&facet.field=autocomplete&indent=true&facet.prefix=duty+
