[
https://issues.apache.org/jira/browse/SPARK-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583826#comment-14583826
]
Eran Medan commented on SPARK-7028:
-----------------------------------
[~srowen] - I completely agreed with you, until I saw this question by someone
new to Spark (And probably to Scala as well):
http://www.reddit.com/r/apachespark/comments/39kzp5/how_to_return_filter_results_that_are_false_to_a/
So it does have some merit to it for "noobs" and by "noobs" I'm also including
non programmers who need to read spark code (e.g. analysts etc).
Apparently filterNot immediately gets understood by non programmers and novice
ones, the ! sign, as you can see from the above link, even to novice
programmers takes a few seconds to get to the "aha" moment. Surprising, but
evident.
So, If I do this fix and add all the unit tests / docs in a pull request, will
you consider changing it from "won't fix" to "won't fix but if someone else
already did and won't stop nagging about it I'll let jenkins an 'ok to test'
and then we'll see, no promises, even if all tests pass"?
> Add filterNot to RDD
> --------------------
>
> Key: SPARK-7028
> URL: https://issues.apache.org/jira/browse/SPARK-7028
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Marius Soutier
> Priority: Minor
>
> The Scala collection APIs have not only `filter`, but also `filterNot` for
> convenience and readability. I'd suggest to add the same to RDD.
> I can submit a PR.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
