# Arrow and Avro

Arrow IPC and Avro are schema-bearing interchange formats. Create explicit destination columns before importing them, then verify that their source types map to the intended CoordinatorDB declarations.

## Choose the container

* `arrow` uses an Arrow IPC file.
* `arrow_stream` uses an Arrow IPC stream.
* `avro` uses an Avro object container.
* `avro_confluent` uses schema identifiers resolved through a configured registry.

ORC is not supported.

## Import workflow

Use native FROM INFILE or attached INSERT FORMAT input. The destination declarations validate decoded values, including numeric ranges, collection members and NULL rules.

For a server file() relation, provide the explicit column/type list even when the container carries a schema. A schema registry is additionally required for the Confluent variant; an ordinary Avro container embeds its record schema.

## Type mappings and options

See [Arrow](https://coordinatordb.com/docs/reference/formats/arrow/arrow), [ArrowStream](https://coordinatordb.com/docs/reference/formats/arrow/arrow-stream), [Avro](https://coordinatordb.com/docs/reference/formats/avro/avro) and [AvroConfluent](https://coordinatordb.com/docs/reference/formats/avro/avro-confluent) for executable examples, supported types and statement settings.