Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/1813
Hi @mjsax,
Regarding 1): just came to me that for SORTED_SET, a fixed secondary key
doesn't make sense, because the secondary key is supposed to define the order
of the inserted element in the set. For HASH, I guess it depends on the use
case. For example, a stream of user events with user id can update Redis using
the user id as primary key, and inner hash field (secondary key) depending on
what event occurred.
I agree with your suggestion to settle with a subset of commands to start
with, and if we want to, make it more flexible for multiple command per data
type with new JIRAs as it would probably need larger refactoring.
---
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.
---
