Mailing-List: contact general-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Wed, 4 May 2011 16:04:26 -0700 (PDT)
From: brandyn <brandyn-kusenda@uiowa.edu>
To: general@lucene.apache.org
Message-ID: <1304550266616-2901365.post@n3.nabble.com>
Subject: autocomplete with Solr using TermComponent
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi. 
I need an autocomplete solution to handle case-insensitive queries but
return the original text with the case still intact.   I've experimented
with both the Suggester and TermComponent methods.  TermComponent is working
when I use the regex option, however, it is far to slow.   I get the speed i
want by using term.prefix for by using the suggester but it's case
sensitive.

Here is an example:

Query: bran
Results: Branden, Brandon, Brandy, Brian, ...

A solution that I would expect to work would be to store two fields; one
containing the original text and the other containing the lowercase.  Then
convert the query to lower case and run the query against the lower case
field and return the original (case preserved) field.
Unfortunately, I can't get a TermComponent query to return additional
fields.  It only returns the field it's searching against.  Should this work
or can I only return additional fields for standard queries.

Thanks in advance.


--
View this message in context: http://lucene.472066.n3.nabble.com/autocomplete-with-Solr-using-TermComponent-tp2901365p2901365.html
Sent from the Lucene - General mailing list archive at Nabble.com.