[
https://issues.apache.org/jira/browse/IGNITE-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666886#comment-15666886
]
Roman Shtykh edited comment on IGNITE-3066 at 11/15/16 11:32 AM:
-----------------------------------------------------------------
3) Actually, this is needed for (almost?) all STRING commands, but we have only
a set of STRING commands supported, so probably we don't need non-string check
for now. What do you think?
On the other hand, if we have an integer value that was injected through Ignite
Cache API, and a user accesses it via Redis client, should we show an error or
convert to string and operate normally?
was (Author: roman_s):
3) Actually, this is needed for all STRING commands, but we have only a set of
STRING commands supported, so probably we don't need non-string check for now.
What do you think?
On the other hand, if we have an integer value that was injected through Ignite
Cache API, and a user accesses it via Redis client, should we show an error or
convert to string and operate normally?
> Set of Redis commands that can be easily implemented via existing REST
> commands
> -------------------------------------------------------------------------------
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
