@terascope/data-mate / teal-frame/schema-check / SchemaMismatch
Interface: SchemaMismatch
Defined in: data-mate/src/teal-frame/schema-check.ts:9
One disagreement between a frame's declared DataTypeConfig and the column types DuckDB
actually produces.
Properties
| Property | Type | Description | Defined in |
|---|---|---|---|
column | string | - | data-mate/src/teal-frame/schema-check.ts:10 |
declared? | FieldType | The FieldType the config declares. Reports lead with this, because DuckDB types are a storage detail. Absent when kind is unexpected (the column was never declared). | data-mate/src/teal-frame/schema-check.ts:15 |
kind | "type" | "missing" | "unexpected" | - | data-mate/src/teal-frame/schema-check.ts:16 |
storage? | object | For diagnosis: the DuckDB type declared maps to, and the type DuckDB actually produced. There is no DuckDB-to-FieldType mapping, because it would be ambiguous (VARCHAR backs Keyword, Text, IP, Binary and more). So types are compared as DuckDB types. | data-mate/src/teal-frame/schema-check.ts:23 |
storage.actual? | string | - | data-mate/src/teal-frame/schema-check.ts:23 |
storage.declared? | string | - | data-mate/src/teal-frame/schema-check.ts:23 |