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/05/30 15:19:04 UTC

[jira] [Updated] (IGNITE-5320) Add well-known SQL schema where SQL caches will "live" by default

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

Vladimir Ozerov updated IGNITE-5320:
------------------------------------
    Summary: Add well-known SQL schema where SQL caches will "live" by default  (was: Add well-known SQL schema where caches will "live" by default)

> Add well-known SQL schema where SQL caches will "live" by default
> -----------------------------------------------------------------
>
>                 Key: IGNITE-5320
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5320
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>             Fix For: 2.1
>
>
> Considerations:
> 1) Schema is always present and is never dropped
> 2) If {{CacheConfiguration.sqlSchema}} is not specified explicitly, cache should reside in default schema.
> 3) There should be a flag on cache configuration to allow fallback to previous behavior, when cache existed in separate schema equal to it's name.
> 4) CREATE TABLE can only create objects in default schema. Throw exception otherwise. That is, this is OK:
> {code}
> CREATE TABLE "default_schema".MyTable ...
> {code}
> And this is not:
> {code}
> CREATE TABLE "non_default_schema".MyTable ...
> {code}



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