Skip to content

[MINOR][ML] update comment where is inconsistent with code in ml.regression.LinearRegression #14121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

WeichenXu123
Copy link
Contributor

What changes were proposed in this pull request?

In train method of ml.regression.LinearRegression when handling situation std(label) == 0
the code replace std(label) with mean(label) but the relative comment is inconsistent, I update it.

How was this patch tested?

N/A

@SparkQA
Copy link

SparkQA commented Jul 10, 2016

Test build #62042 has finished for PR 14121 at commit ab7452c.

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

@srowen
Copy link
Member

srowen commented Jul 10, 2016

OK

@srowen
Copy link
Member

srowen commented Jul 12, 2016

Merged to master/2.0

asfgit pushed a commit that referenced this pull request Jul 12, 2016
…ession.LinearRegression

## What changes were proposed in this pull request?

In `train` method of `ml.regression.LinearRegression` when handling situation `std(label) == 0`
the code replace `std(label)` with `mean(label)` but the relative comment is inconsistent, I update it.

## How was this patch tested?

N/A

Author: WeichenXu <WeichenXu123@outlook.com>

Closes #14121 from WeichenXu123/update_lr_comment.

(cherry picked from commit fc11c50)
Signed-off-by: Sean Owen <sowen@cloudera.com>
@asfgit asfgit closed this in fc11c50 Jul 12, 2016
@WeichenXu123 WeichenXu123 deleted the update_lr_comment branch July 12, 2016 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants