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 Thu, 14 Jul 2016 05:06:20 GMT

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

ASF GitHub Bot commented on FLINK-3034:

Github user subhankarb commented on the issue:

    Hi @kl0u, IMO that is the expected behavior. The sink would not know that if the Redis
is down or not unless it tries to send the next data to the Redis. When ever a new message
reaches the sink it tries to use the connection pool, then an then only it can throw exception
that it can not send the data to Redis.
    You can build a heartbeat mechanism to check periodically that Redis serve is up or down,
and can cancel the job if Redis is down. 
    @mjsax please correct me if my understanding is wrong.  

> 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
>             Fix For: 1.1.0
> Flink does not provide a sink connector for Redis.
> See FLINK-3033

This message was sent by Atlassian JIRA

View raw message