Skip to content

Conversation

@davies
Copy link
Contributor

@davies davies commented Dec 16, 2015

MLlib should use SQLContext.getOrCreate() instead of creating new SQLContext.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, sc is not even used here, so it could be removed.

@jkbradley
Copy link
Member

To confirm: There is no need to use getOrCreate in tests, right?

The other changes look fine.

@davies
Copy link
Contributor Author

davies commented Dec 16, 2015

@jkbradley For tests, they are fine.

@SparkQA
Copy link

SparkQA commented Dec 16, 2015

Test build #47859 has finished for PR 10338 at commit 9ae9bd4.

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

@jkbradley
Copy link
Member

LGTM pending tests

@SparkQA
Copy link

SparkQA commented Dec 16, 2015

Test build #47865 has finished for PR 10338 at commit 518e37c.

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

asfgit pushed a commit that referenced this pull request Dec 16, 2015
MLlib should use SQLContext.getOrCreate() instead of creating new SQLContext.

Author: Davies Liu <[email protected]>

Closes #10338 from davies/create_context.

(cherry picked from commit 27b98e9)
Signed-off-by: Davies Liu <[email protected]>
@asfgit asfgit closed this in 27b98e9 Dec 16, 2015
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