[
https://issues.apache.org/jira/browse/IGNITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-6242:
--------------------------------
Description:
CREATE TABLE automatically creates an IgniteCache naming it
SQL_PUBLIC_\{TABLE\}. So, if a Person table is created you’ll have
SQL_PUBLIC_PERSON cache in the cluster.
If we keep to SQL APIs the cache name is not a big deal but as soon as
key-value, compute, service grid APIs are needed the cache name will be used
here and there looking bizarre.
Let's give a way to pass the cache name into WITH clause parameters set
was:
CREATE TABLE automatically creates an IgniteCache naming it SQL_PUBLIC_{TABLE}.
So, if a Person table is created you’ll have SQL_PUBLIC_PERSON cache in the
cluster.
If we keep to SQL APIs the cache name is not a big deal but as soon as
key-value, compute, service grid APIs are needed the cache name will be used
here and there looking bizarre.
Let's give a way to pass the cache name into WITH clause parameters set
> Passing custom cache name to CREATE TABLE
> -----------------------------------------
>
> Key: IGNITE-6242
> URL: https://issues.apache.org/jira/browse/IGNITE-6242
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.1
> Reporter: Denis Magda
> Assignee: Alexander Paschenko
> Priority: Critical
> Labels: usability
> Fix For: 2.3
>
>
> CREATE TABLE automatically creates an IgniteCache naming it
> SQL_PUBLIC_\{TABLE\}. So, if a Person table is created you’ll have
> SQL_PUBLIC_PERSON cache in the cluster.
> If we keep to SQL APIs the cache name is not a big deal but as soon as
> key-value, compute, service grid APIs are needed the cache name will be used
> here and there looking bizarre.
> Let's give a way to pass the cache name into WITH clause parameters set
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
