huangzhw 08ad6abd04
sort Command lookupKeyRead and lookupKeyWrite are used on the opposite (#8283)
This is a recent problem, introduced by 7471743 (redis 6.0)

The implications are:
The sole difference between LookupKeyRead and LookupKeyWrite is for command
executed on a replica, which are not received from its master client. (for the master,
and for the master client on the replica, these two functions behave the same)!

Since SORT is a write command, this bug only implicates a writable-replica.
And these are its implications:

- SORT STORE will behave as it did before the above mentioned commit (like before
  redis 6.0). on a writable-replica an already logically expired the key would have
  appeared missing. (store dest key would be deleted, instead of being populated
  with the data from the already logically expired key)
- SORT (the non store variant, which in theory could have been executed on
  read-only-replica if it weren't for the write flag), will (in redis 6.0) have a new bug
  and return the data from the already logically expired key instead of empty response.
2021-01-04 10:28:47 +02:00
..
2020-11-09 21:48:56 -08:00
2020-11-25 13:36:21 -08:00
2020-05-05 10:20:48 +02:00
2020-04-24 17:00:03 -07:00
2020-04-24 17:11:21 -07:00
2020-11-08 08:32:38 +02:00
2020-10-27 15:04:18 +02:00
2020-05-05 23:35:08 -04:00
2020-09-29 15:52:13 +03:00
2019-11-19 17:23:47 +08:00
2019-10-02 11:30:20 +02:00
2020-07-24 14:40:19 +08:00
2020-12-24 13:35:41 +08:00
2020-07-21 08:13:05 +03:00
2020-12-13 11:11:29 +02:00