[jira] [Closed] (GEODE-9417) ZRANGE Behavior After Deletion of Key Inconsistent With Redis

["Owen Nichols (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-9417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen Nichols closed GEODE-9417.
-------------------------------

> ZRANGE Behavior After Deletion of Key Inconsistent With Redis
> -------------------------------------------------------------
>
>                 Key: GEODE-9417
>                 URL: https://issues.apache.org/jira/browse/GEODE-9417
>             Project: Geode
>          Issue Type: Bug
>          Components: redis
>            Reporter: Wayne
>            Assignee: Donal Evans
>            Priority: Major
>              Labels: blocks-1.15.0​, redis, unreleased
>             Fix For: 1.15.0
>
>
> After deleting a SortedSet the behavior for ZRANGE differs from native Redis.
>  
> +Reproduction Steps:+
> Add some data to a SortedSet:
>  * ZADD leaderboard 1 "one"
>  * ZADD leaderboard 2 "two"
> Delete the SortedSet with the key "leaderboard":
>  * DEL leaderboard
> Now perform a ZRANGE command on the deleted key
> ZRANGE leaderboard 0 10
>  
> Native Redis returns "(empty array)" where as we return "
> "(error) ERR The server had an internal error please try again".
>  
> The same behavior occurs even if the SortedSet never existed.  For example:
> ZRANGE nonexistent 0 10 will also result in 
> "(error) ERR The server had an internal error please try again".
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)