[
https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Shtykh updated IGNITE-5229:
---------------------------------
Description:
Currently there's no way to switch caches -- all requests go to 'default'.
_Note that this is the switch for only a subset of Redis data structures
(currently only STRINGs) -- for SETs and HASHTABLEs caches will be specified as
keys (see https://issues.apache.org/jira/browse/IGNITE-5241)_
As an idea, we can use {{CONFIG SET parameter value}} to set the current cache,
save it in {{GridRestProcessor}} and use it until the user switches to another
one.
was:
Currently there's no way to switch caches -- all requests go to 'default'.
_Note that this is the switch for only a subset of Redis data structures
(currently only STRINGs) -- for SETs and HASHTABLEs caches will be specified as
keys (see )_
As an idea, we can use {{CONFIG SET parameter value}} to set the current cache,
save it in {{GridRestProcessor}} and use it until the user switches to another
one.
> 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
>
> Currently there's no way to switch caches -- all requests go to 'default'.
> _Note that this is the switch for only a subset of Redis data structures
> (currently only STRINGs) -- for SETs and HASHTABLEs caches will be specified
> as keys (see https://issues.apache.org/jira/browse/IGNITE-5241)_
> As an idea, we can use {{CONFIG SET parameter value}} to set the current
> cache, save it in {{GridRestProcessor}} and use it until the user switches to
> another one.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
