Execution & Triggers

Triggers

A trigger decides when a Function runs. There are four kinds of triggers:

Manually

When you run it

Execute the Function with the tdk fn trigger CLI Command.

On a schedule

At set times

Execute the Function on a cron schedule, regardless of whether upstream data has changed.

On new data

When an input Table receives new data

Execute the Function whenever an input Table receives a new Version.

On a stream rollover

When a staged batch closes

Execute the Function each time a stream worker, such as SQL CDC or Kafka, closes a batch

Automatic orchestration

No matter which trigger fires a function, Tabsdata doesn't run just that one function. It follows the data dependencies and builds an execution plan: the graph of every function that must run as a result, in the correct order, across collections. There is no orchestration for you to wire up.

Pristine state

Every table in an execution plan stays in sync, because new data is only committed if every function in the plan succeeds. A partial failure commits nothing.

Streaming publishers

A normal publisher pulls a batch of data each time it runs. A streaming publisher stays running continuously, creating new table versions as data arrives: for change-data-capture feeds, log tails, and message queues like Kafka.