[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-16 Thread jkbradley
Github user jkbradley commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112574637 This LGTM I'll merge it into master and branch-1.4 @yanboliang Thanks for the PR, and sorry about the delay in merging! We can update the docs on the

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-16 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/spark/pull/6460 --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-111995615 [Test build #34932 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34932/consoleFull) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112017288 [Test build #34932 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34932/console) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112017314 Merged build finished. Test FAILed. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-111994066 Merged build started. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-111993962 Merged build triggered. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112270239 [Test build #34968 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34968/consoleFull) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112270153 Merged build triggered. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112270163 Merged build started. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread yanboliang
Github user yanboliang commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112258204 retest --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112291866 Merged build finished. Test PASSed. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-06-15 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-112291848 [Test build #34968 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34968/console) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread jkbradley
Github user jkbradley commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107100892 @yanboliang Thanks for adding this doc! With so many Python users, this should be very helpful. --- If your project is set up for it, you can reply to this email

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread jkbradley
Github user jkbradley commented on a diff in the pull request: https://github.com/apache/spark/pull/6460#discussion_r31385522 --- Diff: python/pyspark/mllib/regression.py --- @@ -193,18 +198,28 @@ def train(cls, data, iterations=100, step=1.0, miniBatchFraction=1.0,

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread jkbradley
Github user jkbradley commented on a diff in the pull request: https://github.com/apache/spark/pull/6460#discussion_r31385524 --- Diff: python/pyspark/mllib/regression.py --- @@ -389,7 +434,36 @@ class RidgeRegressionWithSGD(object): def train(cls, data, iterations=100,

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107008762 Merged build started. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107008758 Merged build triggered. --- 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

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread yanboliang
Github user yanboliang commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107009193 The length of docstring line for PEP8 standard is 72, so truncate too long line. --- If your project is set up for it, you can reply to this email and have your

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107008906 [Test build #33805 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33805/consoleFull) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread SparkQA
Github user SparkQA commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107018682 [Test build #33805 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33805/consoleFull) for PR 6460 at commit

[GitHub] spark pull request: [SPARK-7916] [MLlib] MLlib Python doc parity c...

2015-05-30 Thread AmplabJenkins
Github user AmplabJenkins commented on the pull request: https://github.com/apache/spark/pull/6460#issuecomment-107018685 Merged build finished. Test PASSed. --- 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