This repository has been archived by the owner on Nov 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #23 from opendatadiscovery/feature/adf-data-flows
Add metadata regarding DataFlows to the adapter
- Loading branch information
Showing
6 changed files
with
137 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# Usage of Purview to generate pipeline | ||
|
||
## Status | ||
|
||
Rejected. | ||
|
||
## Context | ||
|
||
It was analyzed if Microsoft Purview would be useful in terms of gathering metadata in the ODD platform. | ||
|
||
## Decision | ||
|
||
Currently, it looks like Purview will not add additional value to the ADF adapter. | ||
Purview will not be used in the ODD, at least for now. | ||
|
||
### Reasons | ||
|
||
* It shows lineage only for single activities not for the whole pipelines. | ||
* It's based on pipeline runs not on the definition itself, hence it shows lineage for each run. Because of that, the | ||
container or directory could change in each run. | ||
* Lineage is shown "from file perspective", activities performed on a single file by different pipelines are shown in | ||
a single lineage. | ||
* Using Purview brings additional cost for the user, and most of the metadata shown by Purview can be retrieved directly from | ||
ADF API, hence using Purview doesn't look profitable. | ||
|
||
## Consequences | ||
|
||
We will not get additional metadata from Purview. | ||
|
||
# Adding datasets to the lineage | ||
|
||
## Status | ||
|
||
Proposed. | ||
|
||
## Context | ||
|
||
In the current shape, the Azure Data Factory (ADF) adapter shows only lineage between activities. For example: | ||
![img.png](img.png) | ||
The platform isn't showing input and output files for each activity. | ||
It was developed that way because inputs/outputs could be parametrized and because of that we can have different files for | ||
each run, hence it isn't obvious how to show it in the lineage. | ||
|
||
## Decision | ||
|
||
The proposition is to show datasets between activities. For each activity, we should show input and output, in that case, | ||
lineage | ||
should look like this: | ||
`input1 -> task1 -> output1 -> task2 -> output2 -> ...` | ||
If files directories are hardcoded they can be shown directly in the lineage. | ||
It's yet to be decided how to show datasets that can change in each run. | ||
|
||
## Consequences | ||
|
||
Implementing this solution would greatly enhance the capabilities of ODD and its advantages over using ADF Studio directly. | ||
It would add a possibility to show the integration between ADF and different services (S3, Google Cloud Storage, etc) in the | ||
platform. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters