You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/05 08:17:04 UTC
[jira] [Updated] (IGNITE-5319) Fix schema handling in deprecated
"thin" driver.
[ https://issues.apache.org/jira/browse/IGNITE-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-5319:
------------------------------------
Fix Version/s: (was: 2.1)
2.2
> Fix schema handling in deprecated "thin" driver.
> ------------------------------------------------
>
> Key: IGNITE-5319
> URL: https://issues.apache.org/jira/browse/IGNITE-5319
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Fix For: 2.2
>
>
> Currently both drivers behave as follows: when schema is changed, it is converted to cache name automatically. This is wrong. We should do the following:
> 1) Decouple schema name from cache name. Schema name should be separate field. No conversion.
> 2) When JDBC driver is connected, schema is set to the schema target cache belongs to
> 3) Cache name cannot be changed
> 4) Cache name is always passed to all tasks as before
> 5) Schema name is added to these tasks and propagated to respective {{SqlFieldsQuery}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)