[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[ https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh updated IGNITE-5229: - Fix Version/s: 2.1 > 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[ https://issues.apache.org/jira/browse/IGNITE-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shtykh updated IGNITE-5229: - Labels: redis (was: ) > 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 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
was:
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)_
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 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 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)_
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 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.
> 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 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)_
> 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 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 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.
> 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 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 )_
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 -- 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 )_
> 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)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 -- 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.
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 -- 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 --
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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 -- 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.
was:
Currently there's no way to switch caches -- all requests go to 'default'.
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 --
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (IGNITE-5229) Specify caches when using Redis protocol
[
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'.
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'.
> 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)
