ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5319) Fix schema handling in v1 and v2 drivers
Date Wed, 31 May 2017 11:55:04 GMT

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

Vladimir Ozerov updated IGNITE-5319:
------------------------------------
    Description: 
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}}. 

  was:
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 {{SqlFieldsQueryt}}. 


> Fix schema handling in v1 and v2 drivers
> ----------------------------------------
>
>                 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.1
>
>
> 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)

Mime
View raw message