ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishnu Bharathi (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-12986) Redis mget command is broken
Date Thu, 07 May 2020 00:59:00 GMT
Vishnu Bharathi created IGNITE-12986:
----------------------------------------

             Summary: Redis mget command is broken
                 Key: IGNITE-12986
                 URL: https://issues.apache.org/jira/browse/IGNITE-12986
             Project: Ignite
          Issue Type: Bug
            Reporter: Vishnu Bharathi


When trying to use the redis layer for ignite, noticed that the data returned by the mget
command is inconsistent. Hence the mget command is broken. To demostrate here is an example

{code}
127.0.0.1:11211> set a 1
OK
127.0.0.1:11211> set b 2
OK
127.0.0.1:11211> set c 3
OK
(0.98s)
127.0.0.1:11211> mget a b c 
1) "1"
2) "2"
3) "3"
127.0.0.1:11211> mget c b a
1) "1"
2) "2"
3) "3"
127.0.0.1:11211> mget a c b
1) "1"
2) "2"
3) "3"
{code}

If you notice, the order of the values returned does not match the order of the values returned.

In order to demonstrate the expected behaviour, will run the same commands against a real
redis instance and paste the output below.

{code}
127.0.0.1:6379> set a 1 
OK
127.0.0.1:6379> set b 2 
OK
127.0.0.1:6379> set c 3
OK
127.0.0.1:6379> mget a b c 
1) "1"
2) "2"
3) "3"
127.0.0.1:6379> mget c b a
1) "3"
2) "2"
3) "1"
127.0.0.1:6379> mget a c b
1) "1"
2) "3"
3) "2"
{code}

This is not only happening on the redis-cli, it is also happening when using redis client
libraries. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message