[ https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040230#comment-16040230 ]
ASF GitHub Bot commented on IGNITE-5229: ---------------------------------------- GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/2098 IGNITE-5229: Specify caches when using Redis protocol. Implemented vi… …a SELECT command. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-5229 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/2098.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2098 ---- commit 90c6d9810d4ead9c47b18a3b87d96c9947c39896 Author: shroman <rsht...@yahoo.com> Date: 2017-06-07T05:43:09Z IGNITE-5229: Specify caches when using Redis protocol. Implemented via SELECT command. ---- > 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.3.15#6346)