Unfortunately, we already use the word *"store"* for many other concepts, like CacheStore and PageStore. I'd prefer to avoid giving it one more meaning.
As already mentioned, *"dataset"* has special meaning for ML folks. *"Bucket" *might give wrong association with bucket in a hash table. On Wed, Oct 17, 2018 at 1:49 PM Igor Sapego <isap...@apache.org> wrote: > Well, the obvious term for me is a "Store" or "MemoryStore", as we already > have persistence store. > > Best Regards, > Igor > > > On Wed, Oct 17, 2018 at 1:19 PM Andrey Kuznetsov <stku...@gmail.com> > wrote: > > > I'm not an ML expert, so 'dataset' term just reminds me of various client > > drivers to access tables from RDBM servers. For me, the only common trait > > of all kinds of Ignite caches is their asociativity. So if we rename them > > I'd suggest something like KVStore. > > > > ср, 17 окт. 2018 г. в 12:56, Alexey Zinoviev <zaleslaw....@gmail.com>: > > > > > From my perspective, the main goal is to make easy the explanation what > > is > > > Ignite on conferences, marketing deals, in papers, in documentation. > And > > > the > > > /cache/ term really reduces the area of Ignite usage in users minds. > > > > > > I don't support the critical changes in code base, but I support all > > > changes > > > that helps the goal described above in this letter. > > > > > > > > > > > > -- > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > -- > > Best regards, > > Andrey Kuznetsov. > > > -- Best regards, Ilya
