Manually Trigger a Function
A manual trigger runs a function on demand. Any function can be triggered this way, including one that already carries a schedule, which makes it the way to test a function before trusting it to a cron mask.
A publisher with no trigger configured runs only when triggered manually. That is the default for publishers, since nothing inside Tabsdata can signal that an external system has new data.
Called tabsdata 2 times (ctrl+o to expand)
Triggering read_orders. The plan covers three functions, since summarize reads orders and write_report reads orders_by_region.
Called tabsdata 4 times (ctrl+o to expand)
Execution committed, 0 failures.
All three ran in dependency order:
┌──────────────┬─────────────┬───────────┐ │ function │ kind │ outcome │ ├──────────────┼─────────────┼───────────┤ │ read_orders │ publisher │ committed │ ├──────────────┼─────────────┼───────────┤ │ summarize │ transformer │ committed │ ├──────────────┼─────────────┼───────────┤ │ write_report │ subscriber │ committed │ └──────────────┴─────────────┴───────────┘
Nothing commits unless every function in the plan succeeds, so a failure in summarize would have left orders at the version it held beforehand.