[jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17336919#comment-17336919
]
Flink Jira Bot commented on FLINK-2151:
---
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, 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: Major
> Labels: stale-major
>
> 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.3.4#803005)
[jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17328983#comment-17328983
]
Flink Jira Bot commented on FLINK-2151:
---
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> 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: Major
> Labels: stale-major
>
> 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.3.4#803005)
[jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 API.
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
(v6.3.4#6332)
[jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958913#comment-14958913
]
Wilmer DAZA commented on FLINK-2151:
Hello guys
I was wondering if there is already a plan to integrate Flink with Cassandra?
(read/write tables, send queries en CQL, etc).
I am more interested in writing to cassandra tables from the Stream API of
Flink, but i guess that an integration would require not just writing from
DataStream but a whole complete connector with many other common functionalities
I am making this comment here because I'm guessing that maybe some work in such
a connector may be already started.
Thank you
> 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)
[jira] [Commented] (FLINK-2151) Provide interface to distinguish close() calls in error and regular cases
[
https://issues.apache.org/jira/browse/FLINK-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14571704#comment-14571704
]
Stephan Ewen commented on FLINK-2151:
-
For rich functions, we can add a {{signalCancel()}} methods. That breaks
nothing, because they are regular classes.
For data sinks, it is more tricky. We can add a {{CancelableSink}}
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)
