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 bother you but as soon
as key-value, compute, service grid APIs are needed the cache name will be used
here and there looking bizarre.
Let me propose the following usability improvements until our user does this:
- *At least*
Give a way to pass the cache name into WITH clause parameters set
- *Ideally*
Support the above and if the cache already exists use it instead of creating a
new one. This might help to resolve another issue brought up here:
http://apache-ignite-developers.2346864.n4.nabble.com/CREATE-TABLE-usage-from-Java-API-NET-C-td21455.html
What do you think? If everyone is ok, I’ll file a JIRA ticket.
—
Denis
