-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
[SPARK-13893][SQL] Remove SQLContext.catalog/analyzer (internal method) #11716
Conversation
cc @cloud-fan one more ... |
@@ -113,8 +113,6 @@ class HiveContext private[hive]( | |||
@transient | |||
protected[sql] override lazy val sessionState = new HiveSessionState(self) | |||
|
|||
protected[sql] override def catalog = sessionState.catalog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this is the last one :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are more actually ... in sqlcontext
LGTM |
@cloud-fan Had an extra minute - I went ahead and removed analyzer as well. |
LGTM |
Test build #53177 has finished for PR 11716 at commit
|
Test build #53174 has finished for PR 11716 at commit
|
Thanks - merging in master. |
## What changes were proposed in this pull request? Our internal code can go through SessionState.catalog and SessionState.analyzer. This brings two small benefits: 1. Reduces internal dependency on SQLContext. 2. Removes 2 public methods in Java (Java does not obey package private visibility). More importantly, according to the design in SPARK-13485, we'd need to claim this catalog function for the user-facing public functions, rather than having an internal field. ## How was this patch tested? Existing unit/integration test code. Author: Reynold Xin <rxin@databricks.com> Closes apache#11716 from rxin/SPARK-13893.
What changes were proposed in this pull request?
Our internal code can go through SessionState.catalog and SessionState.analyzer. This brings two small benefits:
More importantly, according to the design in SPARK-13485, we'd need to claim this catalog function for the user-facing public functions, rather than having an internal field.
How was this patch tested?
Existing unit/integration test code.