flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
Date Mon, 19 Oct 2015 14:16:05 GMT

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

Fabian Hueske commented on FLINK-2151:

Hi [~wilmer], I am not aware of an effort to implement a Cassandra data sink for the DataStream
Please open a corresponding JIRA issue if you would like to work on this. It would be good
to have a look at the code and describe your approach before starting with the actual implementation
to make sure that you are going in the right direction.
Cheers, Fabian

> Provide interface to distinguish close() calls in error and regular cases
> -------------------------------------------------------------------------
>                 Key: FLINK-2151
>                 URL: https://issues.apache.org/jira/browse/FLINK-2151
>             Project: Flink
>          Issue Type: Improvement
>          Components: Local Runtime
>    Affects Versions: 0.9
>            Reporter: Robert Metzger
> I was talking to somebody who is interested in contributing a {{flink-cassandra}} connector.
> The connector will create cassandra files locally (on the TaskManagers) and bulk-load
them in the {{close()}} method.
> For the user functions it is currently not possible to find out whether the function
is closed due to an error or an regular end.
> The simplest approach would be passing an additional argument (enum or boolean) into
the close() method, indicating the type of closing.
> But that would break all existing code.
> Another approach would add an interface that has such an extended close method {{RichCloseFunction}}.

This message was sent by Atlassian JIRA

View raw message