v1

latestOpenAPI 3.1.1Apache 2.02026-07-2654130166.5 KB

Table

Metadata

Drop a table

Drop table id and delete its data.

REST NAMESPACE ONLY REST namespace does not use a request body for this operation. The DropTableRequest information is passed in the following way:

post/v1/table/{id}/drop

Response of DropTable

contextContext

Arbitrary context as key-value pairs. How to use the context is custom to the specific implementation.

On a request, it carries caller-provided context to the implementation. On a response, it carries implementation-provided context back to the caller.

REST NAMESPACE ONLY Context entries are mapped to and from HTTP headers using the header. prefix:

On a request, any entry whose key starts with header. is sent as an HTTP request header with the prefix stripped. For example, the entry {"header.Authorization": "Bearer abc"} is sent as the request header Authorization: Bearer abc.
On a response, every HTTP response header is returned as an entry whose key is the header name prefixed with header.. For example, the response header x-request-id: abc123 is returned as the entry {"header.x-request-id": "abc123"}.

transaction_idstring

Optional transaction identifier

idstring[]

locationstring

propertiesobject nullable

If the implementation does not support table properties, it should return null for this field. Otherwise it should return the properties.

{
  "properties": {
    "owner": "Ralph",
    "created_at": "1452120468"
  }
}