-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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-14410][SQL] Push functions existence check into catalog #12198
Conversation
Test build #55089 has finished for PR 12198 at commit
|
bfd8d5f
to
6abe10b
Compare
Test build #55093 has finished for PR 12198 at commit
|
Test build #55146 has finished for PR 12198 at commit
|
@@ -152,6 +152,8 @@ abstract class ExternalCatalog { | |||
|
|||
def getFunction(db: String, funcName: String): CatalogFunction | |||
|
|||
def functionExists(db: String, funcName: String): Boolean |
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.
Great!
LGTM. Merging to master. We will take care the exception handling in getFunctionOption with the work of https://issues.apache.org/jira/browse/SPARK-14414. |
What changes were proposed in this pull request?
This is a followup to #12117 and addresses some of the TODOs introduced there. In particular, the resolution of database is now pushed into session catalog, which knows about the current database. Further, the logic for checking whether a function exists is pushed into the external catalog.
No change in functionality is expected.
How was this patch tested?
SessionCatalogSuite
,DDLSuite