feat: allow querying of json objects stored as strings

[romange]

No description provided.

[chakaz]

Maybe add a unit test?

[BagritsevichStepan]

What are we trying to achieve here? As I understand from the issue submitted by the user, they will store JSON just as blob strings. In this case, the basic GET command will be used to get the JSON blob.

Also, we are converting the blob string into JsonType here. Can you confirm that the reordering of elements does not occur after this conversion?

Redis does not support this behavior:

127.0.0.1:6379> SET mykey '{"name": "John", "age": 30}'
OK
127.0.0.1:6379> JSON.GET mykey
(error) Existing key has wrong Redis type

And still other JSON commands are not supported.

[romange]

Yes, it's an extra behavior that allows some runtime flexibility - a user can query strings that hold json objects. The main thing - it extends Redis behavior, so I do not see a problem here.
The ordering issue stays with JSON.GET of course, but now a user can fetch parts of the object, not the whole string, or use GET to fetch the string as is.

[BagritsevichStepan]

Yes, it's an extra behavior that allows some runtime flexibility - a user can query strings that hold json objects. The main thing - it extends Redis behavior, so I do not see a problem here. The ordering issue stays with JSON.GET of course, but now a user can fetch parts of the object, not the whole string, or use GET to fetch the string as is.

Are we going to support all other JSON.* commands for blob strings?

[romange]

I think we may support additional read only commands but for now I would not rush to do so. Lets wait to see if community finds it useful.