Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-20198

Remove the inconsistency in table/function name conventions in SparkSession.Catalog APIs

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.2, 2.1.1, 2.2.0
    • 2.2.0
    • SQL
    • None

    Description

      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

      It is desirable to make them more consistent with the other Catalog APIs, updates the function/API comments and adds the `@params` to clarify the inputs we allow.

      Attachments

        Issue Links

          Activity

            People

              smilegator Xiao Li
              smilegator Xiao Li
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: