[
https://issues.apache.org/jira/browse/FLINK-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350673#comment-15350673
]
ASF GitHub Bot commented on FLINK-3034:
---------------------------------------
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?
> Redis SInk Connector
> --------------------
>
> Key: FLINK-3034
> URL: https://issues.apache.org/jira/browse/FLINK-3034
> Project: Flink
> Issue Type: New Feature
> Components: Streaming Connectors
> Reporter: Matthias J. Sax
> Assignee: Subhankar Biswas
> Priority: Minor
>
> Flink does not provide a sink connector for Redis.
> See FLINK-3033
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
