Sergi, Vovan, One of Ignite users struggled with an SQL issue and asked me to help him troubleshooting it. The root of the issue was trivial. The guy used a custom object as a key's type but passed the key of “int” type to DML queries.
Honestly, I could spot it only after looking into the code because the exception generated by both H2 and Ignite was useless. Caused by: org.h2.jdbc.JdbcSQLException: Hexadecimal string with odd number of characters: "100"; SQL statement: SELECT TABLE._KEY, TABLE.ID, TABLE.NAME, TABLE.COUNTRY FROM TABLE(_KEY OTHER=(?1,), ID BIGINT=(?2,), NAME VARCHAR=(?3,), COUNTRY VARCHAR=(?4,)) [90003-195 Let’s improve the usability here. The ticket is ready: https://issues.apache.org/jira/browse/IGNITE-5250 <https://issues.apache.org/jira/browse/IGNITE-5250> Do you think add some hint in the nearest release? — Denis
