Re: Override cache name created with CREATE TABLE

1. Here is a ticket since we’re on the same page: https://issues.apache.org/jira/browse/IGNITE-6242 2. Ok, let’s wait for a while. Predicting that this will be supported on day due to users’ feedback :) — Denis > On Aug 31, 2017, at 12:49 AM,

Re: Override cache name created with CREATE TABLE

1) *At least*.- I am ok, makes sense 2) *Ideally* - strong no. Product should not have subtle behavior without a strong reason. I do not see justification for this change. On Thu, Aug 31, 2017 at 4:19 AM, Dmitriy Setrakyan wrote: > I think Denis' idea makes sense. > > Vladimir, what do you think

Re: Override cache name created with CREATE TABLE

I think Denis' idea makes sense. Vladimir, what do you think? D. On Wed, Aug 30, 2017 at 2:57 AM, Denis Magda wrote: > Igniters, > > That’s one more feedback about CREATE TABLE usage in practice. > > The command automatically creates an IgniteCache naming it > SQL_PUBLIC_{TABLE}. So, if a Pers

Override cache name created with CREATE TABLE

Igniters, That’s one more feedback about CREATE TABLE usage in practice. The command 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. Honestly, if you keep to SQL APIs the cache name won’t bo