[
https://issues.apache.org/jira/browse/FLINK-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736449#comment-14736449
]
ASF GitHub Bot commented on FLINK-1730:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1083#issuecomment-138825832
Hi @sachingoel0101,
I think there was no consensus in the discussion (FLINK-1730) for how to
implement this feature. @StephanEwen pointed that persisting data sets should
happen on the network stack level, i.e., not on the operator level. In fact,
this feature was considered and while redesigning and implementing the network
stack by @uce. By doing it on the network stack level, persisted data sets can
also be used for failure recovery or used across different jobs within a
session.
This PR is basically ignoring the previous discussion and features of the
network stack.
If you think that persisting on an operator level has advantages over the
network stack, it would be good to share your thoughts with the community.
Unless there are good reasons to do persisting on operator level, I would
not merge this PR.
> Add a FlinkTools.persist style method to the Data Set.
> ------------------------------------------------------
>
> Key: FLINK-1730
> URL: https://issues.apache.org/jira/browse/FLINK-1730
> Project: Flink
> Issue Type: New Feature
> Reporter: Stephan Ewen
> Priority: Minor
>
> I think this is an operation that will be needed more prominently. Defining a
> point where one long logical program is broken into different executions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
