Skip to content

Commit d102a20

Browse files
Merge pull request #292842 from jatinsharma-msft/updateMDFCacheSinkDoc
Add details about Data Flow Cache Sink Write to activity output
2 parents d98f6eb + 7e94103 commit d102a20

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/data-factory/data-flow-sink.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,10 @@ For example, if I specify a single key column of `column1` in a cache sink calle
103103
> [!NOTE]
104104
> A cache sink must be in a completely independent data stream from any transformation referencing it via a cache lookup. A cache sink also must be the first sink written.
105105
106-
**Write to activity output** The cached sink can optionally write your output data to the input of the next pipeline activity. This will allow you to quickly and easily pass data out of your data flow activity without needing to persist the data in a data store.
106+
**Write to activity output**
107+
The Cache sink can optionally write its data to the output of the Data Flow activity which can then be used as an input to another activity in the pipeline. This will allow you to quickly and easily pass data out of your data flow activity without needing to persist the data in a data store.
108+
109+
Note that the output from Data Flow that is injected directly into your pipeline is limited to 2MB. Thus, Data Flow will attempt to add to output as many rows as it can while staying within the 2MB limit, therefore sometimes you may not see all of the rows in the activity output. Setting "First row only" at the Data Flow activity level also helps you to limit the data output from Data Flow if needed.
107110

108111
## Update method
109112

0 commit comments

Comments
 (0)