pub struct TableExistsResponse {
pub context: Option<HashMap<String, String>>,
}Expand description
TableExistsResponse : Response for a table existence check. The REST namespace does not transmit this object directly (see the TableExists operation for how the status-code response maps to it). It is the standard data model for the LanceNamespace interfaces (e.g. Java, Python).
Fields§
§context: Option<HashMap<String, String>>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\"}.
Implementations§
Source§impl TableExistsResponse
impl TableExistsResponse
Sourcepub fn new() -> TableExistsResponse
pub fn new() -> TableExistsResponse
Response for a table existence check. The REST namespace does not transmit this object directly (see the TableExists operation for how the status-code response maps to it). It is the standard data model for the LanceNamespace interfaces (e.g. Java, Python).
Trait Implementations§
Source§impl Clone for TableExistsResponse
impl Clone for TableExistsResponse
Source§fn clone(&self) -> TableExistsResponse
fn clone(&self) -> TableExistsResponse
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more