flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3034) Redis SInk Connector
Date Sat, 25 Jun 2016 13:05:37 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349640#comment-15349640

ASF GitHub Bot commented on FLINK-3034:

Github user tzulitai commented on the issue:

    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.

> 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

View raw message