Yakov,
Thank you for the pointers! Let's implement it with SELECT then, with
'redis-ignite-internal-cache-0' as a default one.
Sorry, I was wrong about the number of databases, just remembered there was a
limit. I should have had to recheck.
-- Roman
On Friday, May 19, 2017 6:29 PM,
Roman, your description seems fine to me. I don't like CLIENT SETNAME. This
may confuse redis users as well.
Why do you say that we will have only 8 databases. As far as I remember
there are 16 by default and this is configurable and can be increased as
well. Can you please check this?
To get
Yakov,
Thanks for sharing your thoughts!
I agree that both configuration and CONFIG SET lack flexibility. Let’s forget
about these approaches.
For specifying cache per connection, CLIENT SETNAME [cache_name] [1] can be
another option. It can be done with config templates as you proposed too.
Roman,
I don't like implementing of special configuration type - you loose
flexibility in this case, e.g. adding cache will most likely be a pain or a
complete restart. CONFIG SET may work, but for redis this is some kind of
global configuration, so it is pretty far from, let's say, MySQL's USE
Igniters,
Getting back to the discussion on how to switch between caches when using Redis
(and potentially memcached).# Please note, that this is a problem only with a
part of Redis data stuctures such as currently implemented STRING. For sets and
hash tables, set/hash name can be treated as a
