On this page
Append to a streaming table¶
write_target.type: streaming_table. The mode field selects the flow shape.
Minimal example¶
Add this entry to the actions list in your flowgroup.
- name: write_customer_silver
type: write
source: v_customer_bronze
write_target:
type: streaming_table
mode: standard
catalog: "${catalog}"
schema: "${silver_schema}"
table: customer_dim
Options¶
Key |
Type |
Default |
Notes |
|---|---|---|---|
|
string |
|
One of |
source may be a single view or a list of views (multi-source append flow
into one table).
Generates dp.create_streaming_table(...) when create_table is true,
plus one @dp.append_flow(...) per source view.
An append flow reads its source view with readMode (default stream), and
the read must match the view’s kind. Appending a batch view, such as a delta
load that has no readMode: stream, fails lhp validate with
LHP-VAL-070. Either read it as a stream (readMode: stream on the load),
or set readMode: batch together with once: true to append it once as a
backfill.
Action fields¶
These fields sit on the action, alongside write_target.
Field |
Type |
Default |
Requirement and behaviour |
|---|---|---|---|
|
string |
required |
Action name, unique within the flowgroup. |
|
string |
required |
Always |
|
string / list |
conditional |
Input view(s). Standard streaming writes and most sinks accept a list. CDC, replace, replace_where and foreachbatch use one view. Snapshot CDC takes its source inside |
|
mapping |
required |
Target settings; |
|
string |
derived |
Comment/docstring for the generated flow or view. |
|
string |
|
|
|
bool |
|
Emits |
|
bool / list |
— |
Accepted on the model; writes do not add metadata columns. Select columns on load or supported transform actions instead. |
|
list[string] |
— |
Extra upstream table/view references. See Dependency analysis reference. |