Yep - that's correct. As an optimization we save the shuffle output and
re-use if if you execute a stage twice. So this can make A:B tests like
this a bit confusing.
- Patrick
On Friday, August 22, 2014, Nieyuan <qiushuiwuh...@gmail.com> wrote:
> Because map-reduce tasks like join will save shuffle data to disk . So the
> only diffrence with caching or no-caching version is :
> >> .map { case (x, (n, i)) => (x, n)}
>
>
>
> -----
> Thanks,
> Nieyuan
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Advantage-of-using-cache-tp12480p12634.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@spark.apache.org <javascript:;>
> For additional commands, e-mail: user-h...@spark.apache.org <javascript:;>
>
>
