Push sources are used in cases when some external actor actively sends data into a dataset.

Push sources are suitable for:

  • IoT devices that periodically send data
  • Business processes that report events directly into ODF dataset
  • For ingesting data from streaming data APIs and event queues like Apache Kafka.

Source Metadata

Push sources are added via AddPushSource metadata event:

kind: DatasetSnapshot
version: 1
  name: gps
  kind: Root
    - kind: AddPushSource
      sourceName: default
        kind: NdJson
          - t TIMESTAMP
          - long DOUBLE
          - lat DOUBLE
        kind: Append
    - kind: SetVocab
      eventTimeColumn: t

Note that push sources are named:

sourceName: default

This allows you to declare multiple push sources per dataset, which may be useful for situations where several devices from different manufacturers produce slightly different data, but you want them to be able to write directly to one dataset.

An existing push source can be deactivated using DisablePushSource event.

Also note that, just like polling sources, push sources pass data through a Merge Strategy, so they too can benefit, for example, from event deduplication of the Ledger merge strategy.

Pushing Data via CLI

To push data into dataset via kamu use kamu ingest command.

You can push data from files:

echo '{"t": "2020-01-01T00:00:00Z", "long": -123.12, "lat": 49.28}' > data.json
kamu ingest gps data.json

Or from directly from STDIN:

echo '{"t": "2020-01-01T00:00:00Z", "long": -123.12, "lat": 49.28}' | kamu ingest gps --stdin


kamu tail gps
│ offset │ op │       system_time        │          t           │  long   │  lat  │
0 │ +A │ 2024-01-31T03:51:03.618Z │ 2020-01-01T00:00:00Z │ -123.12 │ 49.28 │

Pushing Data via API

See Kamu Node protocols documentation for various options of pushing data programmatically via APIs.

Format Translation

While push sources define a specific read format for their data - there is some tolerance. For example you can push Csv data to the source that declares NdJson format and kamu will attempt to read it using the same schema.

This behavior works both in CLI commands and in push APIs.