Github user jhu-chang commented on the pull request:
https://github.com/apache/spark/pull/8881#issuecomment-142889379
@srowen Yes, user can write his own logical to deal with the case mentioned
last post. But user may still try to use the exist API like
```saveAsXXXFiles``` first rather than start a new one, even though it is very
simple for us.
About the lineage, I totally agree with you: user must know that the side
affect of empty rdd, but as a junior in spark, he/she may not aware of this
(Well document may help him/her), In this aspect, return ```None``` has no
difference with empty RDD if he/she knows what he/she does. So if ```None```
will introduce undefined behavior, the empty RDD also will, just depends how
the user uses @jerryshao
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
