Enum MergeKey 

pub enum MergeKey {
    Single(String),
    Multi(Vec<String>),
}

One or many column names. Accepts either a JSON string "col" or a JSON array ["col1", "col2"] for ergonomics — the tool layer normalizes to Vec<String> before passing into the ingest code.

A custom serde::Deserialize implementation produces clear errors for wrong shapes (null, numbers, objects) instead of the default untagged-enum message (“data did not match any variant of untagged enum MergeKey”), which is opaque from the MCP-tool-call side.

Variants

Single(String)

Multi(Vec<String>)

Implementations

impl MergeKey

pub fn into_vec(self) -> Option<Vec<String>>

Materialize as a non-empty Vec<String>, or return None for the empty case so callers can convert it into an InvalidArgument error with a context-appropriate message.

Trait Implementations

impl Debug for MergeKey

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for MergeKey

fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>

where D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for MergeKey

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.