diff options
| author | Xiao Li <gatorsmile@gmail.com> | 2017-04-04 18:57:46 +0800 |
|---|---|---|
| committer | Wenchen Fan <wenchen@databricks.com> | 2017-04-04 18:57:46 +0800 |
| commit | 26e7bca2295faeef22b2d9554f316c97bc240fd7 (patch) | |
| tree | 0d23926689539b4a47b9333d0dbf2018d942172b /docs | |
| parent | c95fbea68e9dfb2c96a1d13dde17d80a37066ae6 (diff) | |
| download | spark-26e7bca2295faeef22b2d9554f316c97bc240fd7.tar.gz spark-26e7bca2295faeef22b2d9554f316c97bc240fd7.tar.bz2 spark-26e7bca2295faeef22b2d9554f316c97bc240fd7.zip | |
[SPARK-20198][SQL] Remove the inconsistency in table/function name conventions in SparkSession.Catalog APIs
### What changes were proposed in this pull request?
Observed by felixcheung , in `SparkSession`.`Catalog` APIs, we have different conventions/rules for table/function identifiers/names. Most APIs accept the qualified name (i.e., `databaseName`.`tableName` or `databaseName`.`functionName`). However, the following five APIs do not accept it.
- def listColumns(tableName: String): Dataset[Column]
- def getTable(tableName: String): Table
- def getFunction(functionName: String): Function
- def tableExists(tableName: String): Boolean
- def functionExists(functionName: String): Boolean
To make them consistent with the other Catalog APIs, this PR does the changes, updates the function/API comments and adds the `params` to clarify the inputs we allow.
### How was this patch tested?
Added the test cases .
Author: Xiao Li <gatorsmile@gmail.com>
Closes #17518 from gatorsmile/tableIdentifier.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions