Skip to content

Conversation

@jkbradley
Copy link
Member

What changes were proposed in this pull request?

Several classes and methods have been deprecated and are creating lots of build warnings in branch-2.0. This issue is to identify and fix those items:

  • WithSGD classes: Change to make class not deprecated, object deprecated, and public class constructor deprecated. Any public use will require a deprecated API. We need to keep a non-deprecated private API since we cannot eliminate certain uses: Python API, streaming algs, and examples.
    • Use in PythonMLlibAPI: Change to using private constructors
    • Streaming algs: No warnings after we un-deprecate the classes
    • Examples: Deprecate or change ones which use deprecated APIs
  • MulticlassMetrics fields (precision, etc.)
  • LinearRegressionSummary.model field

How was this patch tested?

Existing tests. Checked for warnings manually.

@srowen
Copy link
Member

srowen commented May 26, 2016

LGTM. I will do one more pass to clear up build warnings before the final release so I might be able to clean up stragglers, if any, later

@SparkQA
Copy link

SparkQA commented May 26, 2016

Test build #59321 has finished for PR 13314 at commit cae67d6.

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

@holdenk
Copy link
Contributor

holdenk commented May 26, 2016

@srowen willing to help with that too btw :)

@jkbradley
Copy link
Member Author

Thanks! I'll merge this with master and branch-2.0 then.

@jkbradley
Copy link
Member Author

I'll also leave the JIRA open to remind us to check for remaining items.

@asfgit asfgit closed this in b0a03fe May 26, 2016
asfgit pushed a commit that referenced this pull request May 26, 2016
…recations

## What changes were proposed in this pull request?

Several classes and methods have been deprecated and are creating lots of build warnings in branch-2.0. This issue is to identify and fix those items:
* WithSGD classes: Change to make class not deprecated, object deprecated, and public class constructor deprecated. Any public use will require a deprecated API. We need to keep a non-deprecated private API since we cannot eliminate certain uses: Python API, streaming algs, and examples.
  * Use in PythonMLlibAPI: Change to using private constructors
  * Streaming algs: No warnings after we un-deprecate the classes
  * Examples: Deprecate or change ones which use deprecated APIs
* MulticlassMetrics fields (precision, etc.)
* LinearRegressionSummary.model field

## How was this patch tested?

Existing tests.  Checked for warnings manually.

Author: Sean Owen <sowen@cloudera.com>
Author: Joseph K. Bradley <joseph@databricks.com>

Closes #13314 from jkbradley/warning-cleanups.

(cherry picked from commit b0a03fe)
Signed-off-by: Joseph K. Bradley <joseph@databricks.com>
@jkbradley jkbradley deleted the warning-cleanups branch May 26, 2016 21:28
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.

4 participants