[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-2151:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Runtime / Task
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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
(v8.20.1#820001)
