[msiddalingaiah]

Rewording was based on this discussion: http://apache-spark-developers-list.1001551.n3.nabble.com/RDD-data-flow-td9804.html
This is the associated JIRA ticket: https://issues.apache.org/jira/browse/SPARK-4884

[AmplabJenkins]

Can one of the admins verify this patch?

[ash211]

Ok to test

[ash211]

Also @msiddalingaiah commits should typically have a SPARK jira ticket associated with them so we can properly credit contributors when we do release notes, plus tie a commit back to discussion on a Jira ticket. Would you mind filing a ticket (even for this small change) and add it to the title?

The preferred contribution process is documented here: https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark

This particular commit is so small it's hardly worth the effort, but I do think it's a good habit to get into for even the smallest of changes for future contributors looking to track the history of a change.

Thanks!

[ash211]

ok to test

[SparkQA]

Test build #24573 has started for PR 3722 at commit 79e679f.

• This patch merges cleanly.

[SparkQA]

Test build #24573 has finished for PR 3722 at commit 79e679f.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[AmplabJenkins]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/24573/
Test PASSed.

[msiddalingaiah]

@ash211 Not a problem, I created a JIRA ticket and updated the title/description.
I can't seem to assign the issue to myself, can you help with that?
Thanks!!

[ash211]

+1

[JoshRosen]

LGTM, so I've merged this into all of the maintenance branches + master. Thanks!