Skip to content

Commit fe4048e

Browse files
Update data-flow-sink.md
Fixed typos
1 parent aef469d commit fe4048e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ Select **Validate schema** to fail the sink if the schema changes.
4949
Select **Clear the folder** to truncate the contents of the sink folder before writing the destination files in that target folder.
5050

5151
## Fixed mapping vs. rule-based mapping
52-
When you turn-off auto-mapping, you will have the option to add either column-based mapping (fixed mapping) or rule-based mapping. Rule-based mapping will allow you to write expressions with pattern matching while fixed mapping will map logical and physical column names.
52+
When you turn off auto-mapping, you will have the option to add either column-based mapping (fixed mapping) or rule-based mapping. Rule-based mapping will allow you to write expressions with pattern matching while fixed mapping will map logical and physical column names.
5353

5454
![Rule-based Mapping](media/data-flow/rules4.png "Rule-based mapping")
5555

@@ -65,7 +65,7 @@ A very basic common example for a rule-based mapping vs. fixed mapping is the ca
6565

6666
### Sink association with dataset
6767

68-
The dataset that you select for your sink may or may not have a schema defined in the dataset definition. If it does not have a defined schema, then you must allow schema drift. When you defined a fixed mapping, the logical-to-physical name mapping will persist in the sink transformation. If you change the schema definition of the dataset, then you will potentionally break your sink mapping. To avoid this, use rule-based mapping. Rule-based mappings are generlized, meaning that schema changes on your dataset will not break the mapping.
68+
The dataset that you select for your sink may or may not have a schema defined in the dataset definition. If it does not have a defined schema, then you must allow schema drift. When you defined a fixed mapping, the logical-to-physical name mapping will persist in the sink transformation. If you change the schema definition of the dataset, then you will potentially break your sink mapping. To avoid this, use rule-based mapping. Rule-based mappings are generalized, meaning that schema changes on your dataset will not break the mapping.
6969

7070
## File name options
7171

0 commit comments

Comments
 (0)