[jira] [Updated] (IGNITE-4141) JDBC driver should always set withKeepBinary flag when querying cache

["Evgenii Zhuravlev (JIRA)" <ji...@apache.org>]

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

Evgenii Zhuravlev updated IGNITE-4141:
--------------------------------------

Done. Link to tc: http://ci.ignite.apache.org/project.html?projectId=IgniteTests&tab=projectOverview&branch_IgniteTests=pull%2F1617%2Fmerge. Link to upsource :http://reviews.ignite.apache.org/ignite/review/IGNT-CR-118. PR: https://github.com/apache/ignite/pull/1617

> JDBC driver should always set withKeepBinary flag when querying cache
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-4141
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4141
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc-driver, SQL
>    Affects Versions: 1.7
>            Reporter: Valentin Kulichenko
>            Assignee: Evgenii Zhuravlev
>
> Generally there are no model classes on the client which uses JDBC driver. This means that an attempt to query {{_key}} and {{_val}} fields (which are included in {{select *}}) will fail with "Failed resolve class for ID" error. To avoid this we should always set {{withKeepBinary()}} flag when executing query on server side.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)