If you really need wildcards on both ends, I don't think edgengram will work, you need plain ngrams. The trick is that the query side needs to make the 2-grams into phrases. BTW, I think you'd be fine with bigrams.....
Best Erick On Thu, Aug 8, 2013 at 1:47 PM, meena.sri...@mathworks.com < meena.sri...@mathworks.com> wrote: > Thanks for your responses, helped me to understand the issue. Digged > through > the documentation and now I am implementing EdgeNGramFilterFactory to see > how fastly can I improve wild card searches. > > <fieldType name="type_wildcard" class="solr.TextField"> > <analyzer type="index"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.WordDelimiterFilterFactory" > generateWordParts="1" generateNumberParts="1" catenateWords="0" > catenateNumbers="0" catenateAll="0" splitOnCaseChange="1"/> > <filter class="solr.EdgeNGramFilterFactory" minGramSize="2" > maxGramSize="10" side="front" /> > <filter class="solr.StopFilterFactory" ignoreCase="true" > words="stopwords.txt" enablePositionIncrements="true"/> > <filter class="solr.LowerCaseFilterFactory"/> > <filter class="solr.TrimFilterFactory" /> > <filter class="solr.RemoveDuplicatesTokenFilterFactory"/> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.StopFilterFactory" ignoreCase="true" > words="stopwords.txt" enablePositionIncrements="true"/> > <filter class="solr.LowerCaseFilterFactory"/> > <filter class="solr.TrimFilterFactory" /> > </analyzer> > </fieldType> > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-search-on-a-large-text-field-is-very-slow-tp4083310p4083365.html > Sent from the Solr - User mailing list archive at Nabble.com. >
