Discrepancy between documented behavior and actual behavior for JSON.OBJKEYS for nonexistent keys

There is a discrepancy between the documented behavior and actual behavior for JSON.OBJKEYS for nonexistent keys

Documented behavior : Returns null for nonexistent keys.

Observed behavior : ERR could not perform this operation on a key that doesn't exist

Note that with .-based path argument the command returns null as expected.

To align with the behavior of GET and JSON.GET the documented behavior makes more sense in my opinion.

Thank you.
The documentation indeed states that null is returned for nonexistent key.
This is true for .-paths but not for $-paths.

redis> JSON.OBJKEYS no_such_key .
(nil)
redis> JSON.OBJKEYS no_such_key $
(error) ERR could not perform this operation on a key that doesn't exist

We will update the documentation accordingly.

This behavior is consistent with other commands, such as JSON.ARRLEN.

For JSON.GET the reply is (nil) whether the path is a .-path or a $-path.

We cannot solve this inconsistency now without introducing a breaking change.

Navigation Menu