[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-19 Thread JoshRosen
Github user JoshRosen commented on the pull request: https://github.com/apache/spark/pull/2304#issuecomment-56239181 I'm going to merge this one, too, since this won't introduce any backwards incompatibilities and makes the examples more understandable. --- If your project is set up

[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-19 Thread mattf
Github user mattf commented on the pull request: https://github.com/apache/spark/pull/2304#issuecomment-56240307 oh, i deleted this. use https://github.com/apache/spark/pull/2465 instead --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-06 Thread mattf
GitHub user mattf opened a pull request: https://github.com/apache/spark/pull/2304 [SPARK-1701] [PySpark] remove slice terminology from python examples You can merge this pull request into a Git repository by running: $ git pull https://github.com/mattf/spark

[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-06 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/2304#issuecomment-54714149 [QA tests have started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19915/consoleFull) for PR 2304 at commit

[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-06 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/2304#issuecomment-54716023 [QA tests have finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19915/consoleFull) for PR 2304 at commit

[GitHub] spark pull request: [SPARK-1701] [PySpark] remove slice terminolog...

2014-09-06 Thread mattf
Github user mattf closed the pull request at: https://github.com/apache/spark/pull/2304 --- 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