Drop a namespace
Drop namespace id from its parent namespace.
Request body
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"}.
The mode for dropping a namespace, deciding the server behavior when the namespace to drop is not found. Case insensitive, supports both PascalCase and snake_case. Valid values are:
- Fail (default): the server must return 400 indicating the namespace to drop does not exist.
- Skip: the server must return 204 indicating the drop operation has succeeded.
The behavior for dropping a namespace. Case insensitive, supports both PascalCase and snake_case. Valid values are:
- Restrict (default): the namespace should not contain any table or child namespace when drop is initiated. If tables are found, the server should return error and not drop the namespace.
- Cascade: all tables and child namespaces in the namespace are dropped before the namespace is dropped.
Response
Result of dropping a namespace
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"}.
If the implementation does not support namespace properties, it should return null for this field. Otherwise it should return the properties.
If present, indicating the operation is long running and should be tracked using DescribeTransaction