Connectors

File

sink
Available

Write change events as newline-delimited JSON to a file.

Start streaming
DirectionSink
PlacementRuntime or external
DeliveryEffectively-once (idempotent)
CategoryFile

What it does

The file sink writes each change event as one line of newline-delimited JSON, fsynced to disk after every batch. It is the simplest sink: ideal for local pipelines, testing, and archival.

How it works

  1. 1

    Receives ordered change events from any Zipline source.

  2. 2

    Serializes each event as one line of JSON.

  3. 3

    Appends to your file and fsyncs after every batch for durability.

Use cases

  • Inspect a live change stream locally while building a pipeline.
  • Archive changes as newline-delimited JSON for replay or audit.
  • Feed downstream tools that consume JSON lines.

Highlights

Newline-delimited JSON

One record per line, trivially greppable and streamable.

Durable writes

fsync after every batch.

Zero setup

Just a writable path, no external system to run.

Prerequisites

  • A writable output path

Configure it

YAML
sink:
  type: file
  placement: runtime
  config:
    path: /var/zipline/out/orders.ndjson

sink config

FieldTypeDefaultReqDescription
path path - req Destination file path.

Output is newline-delimited JSON - one record per line - fsynced to disk after every batch.

Pairs well with

Postgres SQL Server

Learn more

Start streaming with File

Follow the first-pipeline guide to wire File into a running pipeline, or jump to the full config reference above.

Start streaming All connectors