search

AbsaOSS / atum-service

Apache License 2.0
5 stars 1 forks source link

Figure out a more natural way to work and identify flows #178

Closed benedeki closed 4 months ago

benedeki commented 5 months ago

Background

Flows are starting to show their values as information over different runs are required. But they are hard to work with and identify.

Questions To Answer

  1. What would be an easy way how to identify flows
  2. And therefore make it easy to work with them.

Desired Outcome

An easy and "user" friendly way, how to identify a flow and request its data. (By user is not meant an end-user, but a user of Atum -either the Atum Agent or Atum Service API).

benedeki commented 5 months ago

An idea emerged Flows are created only when a partitioning is created too. Therefor that partitioning is kind of identifying for the flow. Adding that connection and field of partitioning into flows.flows (the actual json not the foreign key) makes the flow much more identifiable, compared to Flow 1234. Will create a PR.