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
>
