Yeah... I realised it... either way, my use case doesn't really require
case-sensitive searches, so is good for me ;)
Thanks,
Alex
On Sun, May 15, 2016 at 2:06 PM, Vitaly <13vitam...@gmail.com> wrote:
> If you take a closer look, you can notice that the idea is to convert the
> field to lower ca
If you take a closer look, you can notice that the idea is to convert the
field to lower case in insertion/indexing, and then look for a lowercase
match during search. Which means you won't be able to use the same field
for case-sensitive search. Unfortunately, I'm not aware of other ways of
implem
I see, cool :) thanks for the help
Alex
On Sun, May 15, 2016 at 1:49 PM, Vitaly <13vitam...@gmail.com> wrote:
> You can use a case-insensitive field type for this, for example
>
> sortMissingLast="true" omitNorms="true">
>
>
>
>
You can use a case-insensitive field type for this, for example
Of course, you'll have to adjust your datatype/schema to make use of the
new type.
Regards,
Vita
Hi there,
Is there a way to make case-insensitive search queries? The following query
works fine, but only find the entry if sending "Alex" but not finding
anything with "ALEX" or "alex" or "AlEx", etc...
http://xxx.xxx.xxx.xxx:8098/search/query/customers?wt=json&q=firstname_register:Alex
Thanks
