Skip to content
This repository has been archived by the owner on May 29, 2024. It is now read-only.

Pipeline Analysis Functionality #48

Open
epociask opened this issue May 12, 2023 · 0 comments
Open

Pipeline Analysis Functionality #48

epociask opened this issue May 12, 2023 · 0 comments
Assignees
@epociask
Labels
needs more info type: enhancement New feature or request

Comments

@epociask
Copy link
Collaborator

Problem

Current ETL has no way to understand when pipeline collisions occur where components can be reused.

Proposed Solution

Introduce an analysis struct type that analyzes two pipelines with the same PipelineUID for mergability.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@epociask epociask

Labels
needs more info type: enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@epociask