Method: projects.locations.catalogs.databases.tables.rename

• HTTP request
• Path parameters
• Request body
  • JSON representation
• Response body
• Authorization Scopes
• IAM Permissions
• Try it!

Renames an existing table specified by the table ID.

HTTP request

POST https://biglake.googleapis.com/v1/{name=projects/*/locations/*/catalogs/*/databases/*/tables/*}:rename

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
name	string Required. The table's name field is used to identify the table to rename. Format: projects/{project_id_or_number}/locations/{locationId}/catalogs/{catalogId}/databases/{databaseId}/tables/{tableId}

Request body

The request body contains data with the following structure:

JSON representation
{ "newName": string }

Fields
newName	string Required. The new name for the specified table, must be in the same database. Format: projects/{project_id_or_number}/locations/{locationId}/catalogs/{catalogId}/databases/{databaseId}/tables/{tableId}

Response body

If successful, the response body contains an instance of Table.

Authorization Scopes

Requires one of the following OAuth scopes:

• https://www.googleapis.com/auth/bigquery
• https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.

IAM Permissions

Requires the following IAM permission on the name resource:

• biglake.tables.update

For more information, see the IAM documentation.