lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: leading and trailing wildcard query
Date Fri, 06 Nov 2009 06:09:30 GMT
> Please elaborate. What do you mean by *desrever* string?

Try reading in reverse ;).

Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR



----- Original Message ----
> From: A. Steven Anderson <a.steven.anderson@gmail.com>
> To: solr-user@lucene.apache.org
> Sent: Thu, November 5, 2009 5:23:48 PM
> Subject: Re: leading and trailing wildcard query
> 
> >
> > The guilt trick is not the best thing to try on public mailing lists. :)
> >
> 
> Point taken, although not my intention.  I guess I have been spoiled by
> quick replies and was getting to think it was a stupid question.
> 
> Plus, I'm literally gonna get trash talk from my Oracle DBE if I can't make
> this work. ;-)
> 
> We've basically relegated Oracle to handling ingest from which we index Solr
> and provide all search features.  I'd hate to have to succumb to using
> Oracle to service this one special query.
> 
> 
> > The first thing that popped to my mind is to use 2 fields, where the second
> > one contains the desrever string of the first one.
> >
> 
> Please elaborate. What do you mean by *desrever* string?
> 
> 
> > The second idea is to use n-grams (if it's OK to tokenize), more
> > specifically edge n-grams.
> >
> 
> Well, that's the problem.  The field may have non-Latin characters that may
> not have whitespace nor punctuation.
> 
> 
> -- 
> A. Steven Anderson


Mime
View raw message