This repository was archived by the owner on May 29, 2024. It is now read-only.

This repository was archived by the owner on May 29, 2024. It is now read-only.

Pipeline Analysis Functionality #48

Open

Assignees

Labels

needs more infotype: enhancement

opened

on May 12, 2023

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.

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

ethenotethan

Labels

needs more infotype: enhancement

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests