[ https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047677#comment-16047677 ]
Roman Shtykh commented on IGNITE-5229: -------------------------------------- [~anovikov] Thank you for the explanation! I see. So we have a kind of default cache created but with "redis-ignite-internal-cache-0" name. Actually, Alexey Kuznetsov proposed the similar thing before (see http://apache-ignite-developers.2346864.n4.nabble.com/Null-cache-names-td17073.html), but not everyone agrees because we end up with a cache with no backups and probably not properly configured. Probably it can be a special case, when you need to specify or create a cache before running examples. What do you think about it? > Specify caches when using Redis protocol > ---------------------------------------- > > Key: IGNITE-5229 > URL: https://issues.apache.org/jira/browse/IGNITE-5229 > Project: Ignite > Issue Type: Improvement > Affects Versions: 2.0 > Reporter: Roman Shtykh > Assignee: Roman Shtykh > Labels: redis > Fix For: 2.1 > > > Currently there's no way to switch caches -- all requests go to 'default'. > _Note that this is the switch needed only for a subset of Redis data > structures (currently only STRINGs) -- for SETs and HASHTABLEs caches will be > specified as keys (see IGNITE-5241)_ > The solution to be implemented: > 1. A user specifies the cache configuration (template) with predefined name > ‘redis-ignite-internal-cache’ > 2. Then issues ‘SELECT n’, and uses ‘redis-ignite-internal-cache-n’. > Caches are configurable by providing a template. > http://apache-ignite-developers.2346864.n4.nabble.com/Changing-cache-name-when-using-Redis-protocol-td17727.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)