[Gandiva] Wrong filtering using LIKE operator

[asfimport]

[This issue was discovered during internal testing in Dremio in the java layer]

I noticed that the LIKE operator is not behaving as it should per SQL standard. Notably it seems to consider `.` as a wildcard in some occasions:

SELECT A FROM (VALUES('abcde'), ('abc.e'), ('abcd'), ('abc.'), ('abc')) TBL(A) WHERE A LIKE 'abc_%'
abcde
abc.e
abcd
abc.
abc 

SELECT A FROM (VALUES('abcde'), ('abc.e'), ('abcd'), ('abc.'), ('abc')) TBL(A) WHERE A LIKE 'abc.%'
abcde
abc.e
abcd
abc.
abc 

SELECT A FROM (VALUES('abcde'), ('abc.e'), ('abcd'), ('abc.'), ('abc')) TBL(A) WHERE A LIKE 'abc_'
(no result)

SELECT A FROM (VALUES('abcde'), ('abc.e'), ('abcd'), ('abc.'), ('abc')) TBL(A) WHERE A LIKE 'abc.'
(no result)

 

Based on code review it seemed that same issue may be present in Gandiva. This bug is to verify & fix it in Gandiva as well.

Reporter: Siddharth Dave / @siddharthdave
Assignee: Siddharth Dave / @siddharthdave

Related issues:

• [Gandiva][C++] Fix regex to ignore "." character (is duplicated by)

_{Note: This issue was originally created as ARROW-4016. Please see the migration documentation for further details.}

[asfimport]

Praveen Kumar / @praveenbingo:
Was fixed a while back.

[asfimport]

Todd Farmer / @toddfarmer:
Transitioning issue from Resolved to Closed to based on resolution field value.