[ 
https://issues.apache.org/jira/browse/IGNITE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16342903#comment-16342903
 ] 

ASF GitHub Bot commented on IGNITE-3999:
----------------------------------------

GitHub user amirakhmedov opened a pull request:

    https://github.com/apache/ignite/pull/3444

    IGNITE-3999: Support case insensitive search in SQL

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/amirakhmedov/ignite IGNITE-3999

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3444.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3444
    
----
commit 71f5dde9673c2f6810db2125f788fa9eec335ba9
Author: Amir Akhmedov <amir.akhmedov@...>
Date:   2018-01-29T04:52:48Z

    IGNITE-3999: Support case insensitive search in SQL

----


> Support case insensitive search in SQL
> --------------------------------------
>
>                 Key: IGNITE-3999
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3999
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 1.7
>            Reporter: Valentin Kulichenko
>            Priority: Critical
>
> Currently case insensitive search is possible only with the help of 
> {{lower()}} function:
> {code}
> select name from MyValue where lower(name) = 'abc_5'
> {code}
> But this will always be a full scan, even if {{name}} field is indexed.
> We need to correctly support {{VARCHAR_IGNORECASE}} H2 type in Ignite and add 
> a respective property to {{@QuerySqlField}} annotation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to