ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Novikov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5229) Specify caches when using Redis protocol
Date Tue, 13 Jun 2017 04:11:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047395#comment-16047395

Andrey Novikov commented on IGNITE-5229:

Hi [~roman_s],

It ok for me to use cache with name "redis-ignite-internal-cache-0" as template, but on mail
list you specify following scenario:
 > With the approach you proposed, a user 
 > 1. Specifies the cache configuration (template) with predefined name 'redis-ignite-internal-cache'

 > 2. Issues 'SELECT n', and uses 'redis-ignite-internal-cache-n' 

Also I found, that examples for redis client was broken: IgniteCheckedException: Failed to
find cache for given cache name (null for default cache): redis-ignite-internal-cache-0
User should create cache with name 'redis-ignite-internal-cache-0' before first using of Redis
client. I think we should register cache template in Redis listener using org.apache.ignite.Ignite#addCacheConfiguration

In redis-example.py I found selection of database on connect:
r = redis.StrictRedis(host='localhost', port=11211, db=0)
Should we support this?

> 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

View raw message