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 Thu, 08 Jun 2017 11:14:18 GMT

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

Andrey Novikov commented on IGNITE-5229:
----------------------------------------

Hi [~roman_s],

I reviewed your pull request, looks good except following usability problems:
* Before use Redis client user should start cache with name: "redis-ignite-internal-cache-0"
* Cache with name: "redis-ignite-internal-cache-0" will be used as template for create new
cache if user execute SELECT command

As I understand from user list, this is unexpected behavior:

By default client is connected to database '0'. Upon first request from the client IgniteCache
with name "redis-ignite-internal-cache-0" gets created. Same for other databases - "redis-ignite-itnernal-cache-XX".
User can register a config template for these caches. 

[~roman_s], [~yzhdanov] Is that correct?

> 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)

Mime
View raw message