Before you begin: A catalog is configured in Datasets Governance.
If you go back to Datasets Governance, you can see the output created in your catalog.

 |
For each source file, Data Factory Studio registered a dataset in the source catalog.
If the source is an S3 storage, the created datasets have the following name
pattern:
[bucketname]:[folder1]/[folder2]/.../[file-name].[file-version].[file-extension]

|
 |
For each pipeline operation, Data Factory Studio registers an Index activity in Datasets Governance, using one or several source datasets and generating the output dataset.
|
 |
For each output created by the Data Factory Studio pipeline, a dataset can also be generated. If the pipeline task is indexing
in an index unit storage, Data Factory Studio registers a dataset in the index unit content catalog.
|
Note:
When Data Factory Studio detects a new file version (for example, a new version of a CSV file in the S3), it
creates a new dataset, and invalidates all the previous versions of this dataset.