[
https://issues.apache.org/jira/browse/IGNITE-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675701#comment-15675701
]
Roman Shtykh commented on IGNITE-4233:
--------------------------------------
'Redis' category page.
h1. Redis Support
h2. Connect to Ignite using Redis compatible client.
Ignite is partially Redis compliant which enables users to store and retrieve
distributed data from Ignite cache using any Redis compatible client.
In version 1.8.0 only the following commands are supported.
- ECHO
- PING
- QUIT
- GET
- MGET (limitation: not null values returned for non-existing keys)
- SET (limitation: without key expiration)
- MSET
- INCR
- DECR
- INCRBY
- DECRBY
- APPEND
- STRLEN
- GETSET
- SETRANGE
- GETRANGE
- DEL (limitation: number of submitted keys returned)
- EXISTS
- DBSIZE
Cluster nodes accepts Redis requests listening on a particular socket. By
default each Ignite node is listening for incoming requests on
{{\[host\]:11211}}. You can override the host and port using
ConnectorConfiguration class
{quote}
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
...
<property name="connectorConfiguration">
<bean
class="org.apache.ignite.configuration.ConnectorConfiguration">
<property name="host" value="localhost"/>
<property name="port" value="6379"/>
</bean>
</property>
</bean>
{quote}
+Information note(readme.io):+ In Redis, databases are identified by an integer
index, not by a database name. Therefore, currently you cannot switch between
caches by names and only entries from null cache are handled.
> Add documentation for REDIS support
> -----------------------------------
>
> Key: IGNITE-4233
> URL: https://issues.apache.org/jira/browse/IGNITE-4233
> Project: Ignite
> Issue Type: Sub-task
> Affects Versions: 1.8
> Reporter: Andrey Novikov
> Assignee: Roman Shtykh
> Fix For: 1.8
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
