lance_namespace_reqwest_client/models/update_table_request.rs
1/*
2 * Lance Namespace Specification
3 *
4 * This OpenAPI specification is a part of the Lance namespace specification. It contains 2 parts: The `components/schemas`, `components/responses`, `components/examples`, `tags` sections define the request and response shape for each operation in a Lance Namespace across all implementations. See https://lance.org/format/namespace/operations for more details. The `servers`, `security`, `paths`, `components/parameters` sections are for the Lance REST Namespace implementation, which defines a complete REST server that can work with Lance datasets. See https://lance.org/format/namespace/rest for more details.
5 *
6 * The version of the OpenAPI document: 1.0.0
7 *
8 * Generated by: https://openapi-generator.tech
9 */
10
11use crate::models;
12use serde::{Deserialize, Serialize};
13
14/// UpdateTableRequest : Each update consists of a field path and an SQL expression that will be evaluated against the current row's value. Optionally, a predicate can be provided to filter which rows to update.
15#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
16pub struct UpdateTableRequest {
17 #[serde(rename = "identity", skip_serializing_if = "Option::is_none")]
18 pub identity: Option<Box<models::Identity>>,
19 /// 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\"}`.
20 #[serde(rename = "context", skip_serializing_if = "Option::is_none")]
21 pub context: Option<std::collections::HashMap<String, String>>,
22 #[serde(rename = "id", skip_serializing_if = "Option::is_none")]
23 pub id: Option<Vec<String>>,
24 /// Branch to target. When not specified, the main branch is used.
25 #[serde(rename = "branch", skip_serializing_if = "Option::is_none")]
26 pub branch: Option<String>,
27 /// Optional SQL predicate to filter rows for update. Field references must use Lance field path syntax: nested fields use dot-separated segments, literal dots require backtick-quoted segments, and backticks inside quoted segments are doubled.
28 #[serde(rename = "predicate", skip_serializing_if = "Option::is_none")]
29 pub predicate: Option<String>,
30 /// List of field updates as [field_path, expression] pairs. Field paths and expression references must use Lance field path syntax: nested fields use dot-separated segments, literal dots require backtick-quoted segments, and backticks inside quoted segments are doubled.
31 #[serde(rename = "updates")]
32 pub updates: Vec<Vec<String>>,
33 /// Properties stored on the table, if supported by the implementation.
34 #[serde(rename = "properties", skip_serializing_if = "Option::is_none")]
35 pub properties: Option<std::collections::HashMap<String, String>>,
36}
37
38impl UpdateTableRequest {
39 /// Each update consists of a field path and an SQL expression that will be evaluated against the current row's value. Optionally, a predicate can be provided to filter which rows to update.
40 pub fn new(updates: Vec<Vec<String>>) -> UpdateTableRequest {
41 UpdateTableRequest {
42 identity: None,
43 context: None,
44 id: None,
45 branch: None,
46 predicate: None,
47 updates,
48 properties: None,
49 }
50 }
51}
52