[
https://issues.apache.org/jira/browse/IGNITE-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101138#comment-16101138
]
Roman Shtykh commented on IGNITE-5241:
--------------------------------------
[~anovikov] I have started implementing HASH commands, and would be thankful if
you can comment on the approach I take now.
https://github.com/shroman/ignite/commits/IGNITE-5241
As you see, HASH commands are very similar to STRING commands, and it might be
good to extends STRING commands to use as HASH commands. But they sometimes
differ in responses etc, therefore I chose to create another thin package for
HASH commands to implement it as closer to Redis behavior as possible.
> Redis hash table support
> ------------------------
>
> Key: IGNITE-5241
> URL: https://issues.apache.org/jira/browse/IGNITE-5241
> Project: Ignite
> Issue Type: New Feature
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
>
> STRING commands use {{redis-ignite-internal-cache-n}}.
> {{KEY_NAME}} in HASH commands (https://redis.io/commands#hash) can be
> considered as a cache name, and HASH commands can work on
> {{redis-ignite-internal-cache-KEY_NAME}} caches.
> With this, server commands like _SELECT_, _FLUSHDB_, _DBSIZE_ will work only
> on STRING caches (selected by _SELECT_ command). All HASH caches will be
> treated by hash commands.
> _FLASHALL_ will purge all Redis caches.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
