Keep voting for SOLR-8362? You could do your preprocessing in UpdateRequestProcessor chain. There is nothing specifically for Lower/Upper case, but there is a generic scripting one: http://www.solr-start.com/javadoc/solr-lucene/org/apache/solr/update/processor/StatelessScriptUpdateProcessorFactory.html
Regards, Alex. ---- Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/ On 24 June 2016 at 13:42, Jay Potharaju <jspothar...@gmail.com> wrote: > Any ideas on how to handle case insensitive search, string fields and > docvalues in 1 field? > > On Thu, Jun 23, 2016 at 8:14 PM, Alexandre Rafalovitch <arafa...@gmail.com> > wrote: > >> At least you don't need to store the sort field. Or even index, if it is >> docvalues (good for sort). >> >> Regards, >> Alex >> On 24 Jun 2016 9:01 AM, "Jay Potharaju" <jspothar...@gmail.com> wrote: >> >> > yes, that is what i thought. but was checking to see if there was >> something >> > I was missing. >> > Thanks >> > >> > On Thu, Jun 23, 2016 at 12:55 PM, Ahmet Arslan <iori...@yahoo.com.invalid >> > >> > wrote: >> > >> > > Hi Jay, >> > > >> > > I don't think it can be combined. >> > > Mainly because: searching requires a tokenized field. >> > > Sorting requires a single value (token) to be meaningful. >> > > >> > > Ahmet >> > > >> > > >> > > >> > > On Thursday, June 23, 2016 7:43 PM, Jay Potharaju < >> jspothar...@gmail.com >> > > >> > > wrote: >> > > Hi, >> > > I would like to have 1 field that can used for both searching and case >> > > insensitive sorting. As far as i know the only way to do is to have two >> > > fields one for searching (text_en) and one for sorting(lowercase & >> > string). >> > > Any ideas how the two can be combined into 1 field. >> > > >> > > >> > > -- >> > > Thanks >> > > Jay Potharaju >> > > >> > >> > >> > >> > -- >> > Thanks >> > Jay Potharaju >> > >> > > > > -- > Thanks > Jay Potharaju
