Skip to content

Conversation

dilipbiswal
Copy link
Contributor

What changes were proposed in this pull request?

We currently in SparkSession.Builder use SQLContext.getOrCreate. It should probably the the other way around, i.e. all the core logic goes in SparkSession, and SQLContext just calls that.

How was this patch tested?

Made sure existing tests pass.

@dilipbiswal dilipbiswal changed the title [SPARK-13485] Cleanup dependencies between SQLContext and SparkSession [SPARK-15075] [SQL] Cleanup dependencies between SQLContext and SparkSession May 13, 2016
@SparkQA
Copy link

SparkQA commented May 13, 2016

Test build #58589 has finished for PR 13102 at commit 3e8d430.

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

@dilipbiswal
Copy link
Contributor Author

cc @rxin

@rxin
Copy link
Contributor

rxin commented May 18, 2016

Sorry this is not what I meant in the JIRA ticket. What I meant was that we should just save SparkSessions, and then SQLContext calls into that. I didn't mean to literally move the code from SQLContext into SparkSession.

@dilipbiswal
Copy link
Contributor Author

@rxin Thank you reynold for handling this. It was taking me a lot of time to understand the dependencies. Thanks again ..

I will close this now.

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