GitHub user asmith26 opened a pull request:
https://github.com/apache/spark/pull/17565
Issue: Change "slice" vs "partition" in exception messages (and code?)
## What changes were proposed in this pull request?
Came across the term "slice" when running some spark scala code.
Consequently, a Google search indicated that "slices" and "partitions" refer to
the same things; indeed see:
- [This issue](https://issues.apache.org/jira/browse/SPARK-1701)
- [This pull request](https://github.com/apache/spark/pull/2305)
- [This StackOverflow
answer](http://stackoverflow.com/questions/23436640/what-is-the-difference-between-an-rdd-partition-and-a-slice)
and [this
one](http://stackoverflow.com/questions/24269495/what-are-the-differences-between-slices-and-partitions-of-rdds)
Thus this pull request fixes the occurrence of slice I came accross.
Nonetheless, [it would
appear](https://github.com/apache/spark/search?utf8=%E2%9C%93&q=slice&type=)
there are still many references to "slice/slices" - thus I thought I'd raise
this Pull Request to address the issue (sorry if this is the wrong place, I'm
not too familar with raising apache issues).
## How was this patch tested?
(Not tested locally - only a minor exception message change.)
Please review http://spark.apache.org/contributing.html before opening a
pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/asmith26/spark master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/17565.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #17565
----
commit 48d6f57311806e81d659500962a5d6b942094d9d
Author: asmith26 <[email protected]>
Date: 2017-04-07T10:51:22Z
Change exception message from "slices" to "partitions".
----
---
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]
