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 Tue, 12 Jul 2016 16:51:20 GMT

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

ASF GitHub Bot commented on FLINK-3034:

Github user kl0u commented on the issue:

    Hi @subhankarb ! By playing around with the sink during testing, I saw that if Redis goes
down in the middle of the execution of  a job, the job has to wait until the next element
(after the Redis failure) arrives in order to detect that it is down.
    This is not the expected behavior, as we want the job to fail as soon as Redis goes down.
Do you have an idea of why this is happening or how to fix it?

> 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