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

Destination connector

Local JSON

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

Version 0.2.13 community alpha

Local JSON

:::danger

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

:::

Overview

This destination writes data to the local filesystem of the host running Airbyte. Data is written to /tmp/airbyte_local by default. To change this location, modify Airbyte’s LOCAL_ROOT environment variable.

Sync overview

Output schema

Each stream is written to its own file. Each file contains a collection of json objects with three fields:

  • _airbyte_ab_id: a uuid that Airbyte assigns 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 extracted data.

Performance

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. Therefore, /local is substituted with /tmp/airbyte_local by default.

:::caution

Make sure Docker Desktop can access /tmp and /private on MacOS. The /tmp symlink points to /private, so access won’t work otherwise. Allow access through “File sharing” in Settings -> Resources -> File sharing -> add the one or two above folder, then select the “Apply & restart” button.

:::

Example

  • Set destination_path to /local/cars/models.
  • Use the /tmp/airbyte_local default for the local mount.
  • All data is then written to the /tmp/airbyte_local/cars/models directory.

Access replicated files

If Airbyte runs on your computer, open file:///tmp/airbyte_local in your browser to view the replicated data locally. If that fails, or Airbyte runs remotely, 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 specified when you created the destination, using cd /{destination_path}.
  4. List files containing the replicated data using ls.
  5. Run cat {filename} to display the data in a specific file.

You can also copy the output file to your host machine. This command copies it to your current working directory:

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

Note: If you run Airbyte on Windows using Docker backed by WSL2, follow similar steps or see link for another approach.

Namespace support

This destination doesn’t support namespaces.

Changelog

Expand to review
VersionDatePull RequestSubject
0.2.132025-03-2456355Upgrade to airbyte/java-connector-base:2.0.1 to be M4 compatible.
0.2.122024-12-1849908Use a base image: airbyte/java-connector-base:1.0.0
0.2.112022-02-1414641Include lifecycle management
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.