[
https://issues.apache.org/jira/browse/FLINK-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736635#comment-14736635
]
ASF GitHub Bot commented on FLINK-1730:
---------------------------------------
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1083#issuecomment-138868165
I apologize. Like I said before, the way I've implemented this, it seemed
pretty trivial. Foremost, I needed this for something else and decided to take
a shot at it. Missed the finer details, going by your comments.
You're right though. Back-tracking the execution graph will most certainly
be a better solution.
@StephanEwen , am I correct in assuming this functionality will be added
after (or along with) Job Session management?
[As for the memory issue though, if data is to be persisted across jobs,
we'll always have to keep the memory segments allocated even after the job
finishes. This is why I defined a separate owner, which can be later *garbage
collected* through a cache freeing mechanism.]
As far as merging it is considered, I wasn't sure myself from the
beginning. I had actually written an email with a link to my branch for
opinions, but ended up opening a PR instead of sending that. So no worries. I'm
closing this.
> 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)
