[jira] [Created] (IGNITE-13231) Unable to use character in where _key= clause via JDBC Thin, if previously putted within cache API.

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-13231:
----------------------------------------

             Summary: Unable to use character in where _key=<character> clause 
via JDBC Thin, if previously putted within cache API.
                 Key: IGNITE-13231
                 URL: https://issues.apache.org/jira/browse/IGNITE-13231
             Project: Ignite
          Issue Type: Bug
            Reporter: Alexander Lapin


Unable to use character in where _key=<character> clause via JDBC Thin, if 
previously putted within cache API.

Following exception will be got:

{color:#172b4d}{{java.sql.{color:#6554c0}SQLException{color}: 
{color:#6554c0}Failed{color} {color:#0052cc}to{color} parse query. 
{color:#6554c0}Hexadecimal{color} string {color:#0052cc}with{color} odd number 
of characters: {color:#36b37e}"a"{color}; SQL statement:SELECT * FROM 
tableefa88adf_7a52_4cac_9a2b_253c4880a369 {color:#6554c0}WHERE{color} _key = 
{color:#36b37e}'a'{color} 
[{color:#0052cc}90003{color}-{color:#0052cc}199{color}]}}{color}

Reproducer: 
org.apache.ignite.jdbc.thin.JdbcThinCacheToJdbcDataTypesCoverageTest#testCharacterDataType



--
This message was sent by Atlassian Jira
(v8.3.4#803005)