)
compute_that_rdd;
do_actual_unpersist();
}
From: Daniel Siegmann [mailto:daniel.siegm...@velos.io]
Sent: Friday, June 13, 2014 5:38 AM
To: user@spark.apache.org
Subject: Re: Question about RDD cache, unpersist, materialization
I've run into this issue. The goal of caching
();
}
*From:* Daniel Siegmann [mailto:daniel.siegm...@velos.io]
*Sent:* Friday, June 13, 2014 5:38 AM
*To:* user@spark.apache.org
*Subject:* Re: Question about RDD cache, unpersist, materialization
I've run into this issue. The goal of caching / persist seems to be to
avoid recomputing an RDD when
;
do_actual_unpersist();
}
From: Daniel Siegmann [mailto:daniel.siegm...@velos.io]
Sent: Friday, June 13, 2014 5:38 AM
To: user@spark.apache.org
Subject: Re: Question about RDD cache, unpersist, materialization
I've run into this issue. The goal of caching / persist seems to be to avoid
recomputing
(I¡¯ve clarified the statement (1) of my previous mail. See below.)
From: innowireless TaeYun Kim [mailto:taeyun@innowireless.co.kr]
Sent: Friday, June 13, 2014 10:05 AM
To: user@spark.apache.org
Subject: RE: Question about RDD cache, unpersist, materialization
Currently I use
() does not compute the whole partitions.
So, first() cannot be uses for the situation below.
-Original Message-
From: innowireless TaeYun Kim [mailto:taeyun@innowireless.co.kr]
Sent: Wednesday, June 11, 2014 11:40 AM
To: user@spark.apache.org
Subject: Question about RDD cache
Hi,
What I (seems to) know about RDD persisting API is as follows:
- cache() and persist() is not an action. It only does a marking.
- unpersist() is also not an action. It only removes a marking. But if the
rdd is already in memory, it is unloaded.
And there seems no API to forcefully
Subject: Question about RDD cache, unpersist, materialization
Hi,
What I (seems to) know about RDD persisting API is as follows:
- cache() and persist() is not an action. It only does a marking.
- unpersist() is also not an action. It only removes a marking. But if the
rdd is already in memory
