lance-namespace-reqwest-client 0.8.5

/*
 * Lance Namespace Specification
 *
 * 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. 
 *
 * The version of the OpenAPI document: 1.0.0
 * 
 * Generated by: https://openapi-generator.tech
 */

use crate::models;
use serde::{Deserialize, Serialize};

#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)]
pub struct AddVirtualColumnOutputEntry {
    /// Physical output column name
    #[serde(rename = "column")]
    pub column: String,
    /// Field name in the UDF output struct
    #[serde(rename = "struct_field")]
    pub struct_field: String,
    /// Data type of the output column using JSON representation
    #[serde(rename = "data_type")]
    pub data_type: serde_json::Value,
    /// Whether the output column is nullable
    #[serde(rename = "nullable")]
    pub nullable: bool,
    /// User-supplied output field metadata (string key-value pairs)
    #[serde(rename = "metadata", skip_serializing_if = "Option::is_none")]
    pub metadata: Option<std::collections::HashMap<String, String>>,
}

impl AddVirtualColumnOutputEntry {
    pub fn new(column: String, struct_field: String, data_type: serde_json::Value, nullable: bool) -> AddVirtualColumnOutputEntry {
        AddVirtualColumnOutputEntry {
            column,
            struct_field,
            data_type,
            nullable,
            metadata: None,
        }
    }
}