Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/1813
Hi @subhankarb,
Sorry, I just read the code and didn't realize you were using the
`additionalKey` as the `setName` for `SORTED_SET`.
I think this might be quite confusing for Redis users. For Redis users, for
sorted sets the `setName` is considered as the primary key, and the per-value
score in the set is considered the additional / secondary key. It works the
same for the hash data type: the hash fields are considered additional /
secondary keys. So right now, the usage principal for `SORTED_SET` and `HASH`
seems to be opposite to each other?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
