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

ASF subversion and git services commented on IMPALA-12581:
----------------------------------------------------------

Commit 12f2026675f6de42d44310c57fe7037f3dc82f46 in impala's branch 
refs/heads/master from Eyizoha
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=12f202667 ]

IMPALA-12581: Fix issue of ILIKE and IREGEXP not working correctly with 
non-const pattern

This patch fixes the issue where ILIKE and IREGEXP couldn't ignore case
when encountering non-constant patterns.
For example, 'SELECT 'ABC' ILIKE pattern FROM tbl' would return false
when the pattern in tbl is '%b%'.

Tests:
 - Add TestNonConstPatternILike to test_exprs.py to verify the
   effectiveness of the fixing.

Change-Id: I3d66680f5a7660e6a41859754c4230f276e66712
Reviewed-on: http://gerrit.cloudera.org:8080/20785
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> ILIKE and IREGEXP don't work with non-const argument values
> -----------------------------------------------------------
>
>                 Key: IMPALA-12581
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12581
>             Project: IMPALA
>          Issue Type: Bug
>          Components: be
>    Affects Versions: Impala 4.3.0
>            Reporter: Peter Rozsa
>            Assignee: Ye Zihao
>            Priority: Critical
>
> ILIKE and IREGEXP's backend implementation does not set the case-insensitive 
> flag when the argument value is non-constant.
> Example:
> {code:java}
> create table ilike_test (x string, y string);
> insert into ilike_test values ('ABC','b');
> select x ilike concat('%', y, '%') from ilike_test;{code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to