[ 
https://issues.apache.org/jira/browse/IGNITE-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chenjian updated IGNITE-18964:
------------------------------
    Description: 
It's a capture corner case for the IGNITE-12687.

The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle 
consecutive "_" character correctly.

eg:

If we have a escaped table name `a\\_\\_b_c" should be translated to "a__b_c" 
not "a__b_c"

 

Affected version is from 2.9 to 2.14

  was:
It's a capture corner case for the IGNITE-12687.

The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle 
consecutive "_" character correctly.

eg:

If we have a escaped table name `a\\_\\_b\\_c" should be translated to "a__b_c" 
not "a\\__b_c"

 

Affected version is from 2.9 to 2.14


> Fix sql wildcard to java regex translation when involving consecutive 
> wildcard characters
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18964
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18964
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.14
>            Reporter: Chenjian
>            Assignee: Chenjian
>            Priority: Major
>
> It's a capture corner case for the IGNITE-12687.
> The current `SqlListenerUtils.translateSqlWildcardsToRegex` not handle 
> consecutive "_" character correctly.
> eg:
> If we have a escaped table name `a\\_\\_b_c" should be translated to "a__b_c" 
> not "a__b_c"
>  
> Affected version is from 2.9 to 2.14



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

Reply via email to