Advanced Analytica Advanced Analytica: IBOM
← All connectors
Local CSV logo

Destination connector

Local CSV

Send governed data into Local CSV with a clear, practical setup guide.

Version 1.0.2 community alpha

Local CSV

:::danger

Use this destination on a local workstation. It won’t work on Kubernetes.

:::

Overview

Data is written to a directory on the local filesystem of the host running Airbyte. By default, it is written to /tmp/airbyte_local. To change this location, modify the LOCAL_ROOT environment variable for Airbyte.

:::caution

Ensure Docker Desktop can access /tmp. On MacOS, it must also access /private because /tmp links to /private. Otherwise, it won’t work. Allow access through “File sharing” in Settings -> Resources -> File sharing -> add the one or two above folder, then select the “Apply & restart” button.

:::

Sync overview

Output schema

Each stream is written to its own file. Each file contains 3 columns:

  • _airbyte_ab_id: a UUID assigned by Airbyte to each processed event.
  • _airbyte_emitted_at: a timestamp showing when the event was pulled from the data source.
  • _airbyte_data: a JSON blob containing the event data.

Performance considerations

Your filesystem’s write speed limits this integration’s performance.

Supported sync modes

Sync modeSupported?
Full Refresh - OverwriteYes
Full Refresh - AppendYes
Full Refresh - Overwrite + DedupedNo
Incremental Sync - AppendYes
Incremental Sync - Append + DedupedNo

Get started

The destination_path always starts with /local, whether you specify it or not. Any directory nesting within local maps to the local mount.

By default, the LOCAL_ROOT env variable in the .env file is set to /tmp/airbyte_local.

Docker mounts the local mount at LOCAL_ROOT. This means /local is replaced with /tmp/airbyte_local by default.

Example

  • If destination_path is set to /local/cars/models,
  • and the local mount uses the /tmp/airbyte_local default,
  • then all data is written to the /tmp/airbyte_local/cars/models directory.

Access replicated data files

If your Airbyte instance runs on this computer, open file:///tmp/airbyte_local in your browser to view replicated data locally. If that fails, or Airbyte runs on a remote server, follow these steps to access the replicated files:

  1. Access the scheduler container using docker exec -it airbyte-server bash
  2. Go to the default local mount using cd /tmp/airbyte_local
  3. Go to the replicated file directory you specified when creating the destination, using cd /{destination_path}
  4. List files containing the replicated data using ls
  5. Run cat {filename} to display data from a specific file

To copy the output file to your host machine’s current working directory, use this command:

docker cp airbyte-server:/tmp/airbyte_local/{destination_path}/{filename}.csv .

Note: If Airbyte runs on Windows with Docker backed by WSL2, follow similar steps or see link for an alternative approach.

Namespace support

This destination doesn’t support namespaces.

Changelog

Expand to review
VersionDatePull RequestSubject
1.0.22025-03-2155906Upgrade to airbyte/java-connector-base:2.0.1 for M4 compatibility.
1.0.12024-12-1849864Use a base image: airbyte/java-connector-base:1.0.0
1.0.02022-12-2017998Breaking changes: non backwards compatible. Adds delimiter dropdown.
0.2.102022-06-2013932Merging published connector changes
0.2.92022-02-1410256Add ExitOnOutOfMemoryError to java connectors and bump versions
0.2.82021-07-213555Checkpointing: Partial Success in BufferedStreamConsumer (Destination)
0.2.72021-06-093973add AIRBYTE_ENTRYPOINT for kubernetes support
0.2.62021-05-253290Checkpointing: Worker use destination (instead of source) for state
0.2.52021-05-103327don’t split lines on LSEP unicode characters when reading lines in destinations
0.2.42021-05-103289bump all destination versions to support outputting messages
0.2.32021-03-312668Add SupportedDestinationSyncModes to destination specs objects
0.2.22021-03-192460Destinations supports destination sync mode
0.2.02021-03-092238Upgrade all connectors (0.2.0) so protocol allows future / unknown properties
0.1.82021-01-291882Local File Destinations UX change with destination paths
0.1.72021-01-201737Rename destination tables
0.1.62021-01-191708Add metadata prefix to destination internal columns
0.1.52020-12-121294Incremental CSV destination
0.1.42020-11-301038Change jdbc sources to discover more than standard schemas
0.1.32020-11-201021Incremental Docs and Data Model Update
0.1.22020-11-18998Adding incremental to the data model
0.1.12020-11-10895bump versions: all destinations and source exchange rate
0.1.02020-10-21676Integrations Reorganization: Connectors
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.