Wait. Sometimes I get confused because gmail will substitute * for bolding, so in my client it looks like you're searching infix (e.g. leading and trailing wildcards). If that's the case, then your performance will always be poor, it has to enumerate all the terms in the field...
If it's just bolding confusing me, then never mind.... Best Erick On Fri, Aug 19, 2011 at 8:27 PM, O. Klein <kl...@octoweb.nl> wrote: > Terms.prefix was just to compare performance. > > The use case was terms.regex=.*query.* And as Markus pointed out, this will > prolly remain a bottleneck. > > I looked at the Suggester. But like many others I have been struggling to > make it useful. It needs a custom queryConverter to give proper suggestions, > but I havent tried this yet. > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Terms-regex-performance-issue-tp3268994p3269628.html > Sent from the Solr - User mailing list archive at Nabble.com. >
