[
https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047642#comment-16047642
]
Andrey Novikov commented on IGNITE-5229:
----------------------------------------
2. All examples started with configuration file:
examples/config/example-ignite.xml or using ExampleNodeStartup
4. In this case we don't receive exception like this: IgniteCheckedException:
Failed to find cache for given cache name (null for default cache):
redis-ignite-internal-cache-0
{code:java}
CacheConfiguration ccfg = new
CacheConfiguration(GridRedisMessage.DFLT_CACHE_NAME);
ctx.grid().addCacheConfiguration(ccfg);
{code}
And when we try to get cache with given name it will be created using template
configuration if not exists.
{code:java}
ctx.grid().getOrCreateCache(GridRedisMessage.DFLT_CACHE_NAME);
{code}
> 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)
