Or we could extend our SQL commands by "GET BY KEY = X" and "PUT (x1, x2, x3) BY KEY = X" and the IgniteTable could be correct. Agree with Denis that each table in the 3rd normal form is like key-value store. Key-value operations are only subset of rich SQL commands.
The problem with IgniteData that it's too common. Also, it's difficult to understand is it a plural or single object? For instance, the bunch of IgniteTables could be IgniteData. But the set of IgniteData? IgniteDatum? чт, 18 окт. 2018 г. в 4:18, Denis Magda <dma...@apache.org>: > Key-value calls are just primary key based calls. From a user perspective, > it's the same as "SELECT * FROM table WHERE primary_idx = X", just > different API. > > -- > Denis > > On Wed, Oct 17, 2018 at 5:04 PM Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > On Wed, Oct 17, 2018 at 4:58 PM Denis Magda <dma...@apache.org> wrote: > > > > > I've been calling everything "tables" instead of "caches" for a while. > > The > > > main reason is the maturity of our SQL engine - seeing more SQL users > and > > > deployments which talk "tables" language. > > > > > > > > I think "IgniteTable" only implies SQL, not key-value. We need both. > > >
