You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2015/06/03 15:17:38 UTC
[jira] [Created] (FLINK-2151) Provide interface to distinguish
close() calls in error and regular cases
Robert Metzger created FLINK-2151:
-------------------------------------
Summary: 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
(v6.3.4#6332)