Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
Tracked by #180
benedeki opened this issue Mar 18, 2024 · 1 comment · Fixed by #186
Closed
Tracked by #180

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

benedeki opened this issue Mar 18, 2024 · 1 comment · Fixed by #186
Assignees
@benedeki
Labels
spike Proof of concept, research and investigation tasks

Comments

@benedeki
Copy link
Contributor

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 benedeki added the spike Proof of concept, research and investigation tasks label Mar 18, 2024
@benedeki benedeki mentioned this issue Mar 18, 2024
Closed
@benedeki benedeki moved this from 🆕 To groom to 📋 Backlog in CPS small repos project Mar 18, 2024
@benedeki benedeki moved this from 📋 Backlog to 🏗 In progress in CPS small repos project Mar 21, 2024
@benedeki
Copy link
Contributor Author

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.

@benedeki benedeki self-assigned this Apr 4, 2024
benedeki added a commit that referenced this issue Apr 12, 2024
@benedeki
#178: Figure out a more natural way to work and identify flows
14e5dbe 
* Added field `fk_primary_partitioning` column to `flows.flows`
* The field is filled when the flow is created
This was referenced Apr 12, 2024
Merged
Closed
Closed
benedeki added a commit that referenced this issue Apr 15, 2024
@benedeki
#178: Figure out a more natural way to work and identify flows (#186)
7be4f59 
* Added field `fk_primary_partitioning` column to `flows.flows`
* The field is filled when the flow is created
* added unique index on flows.flows table field `fk_primary_partitioning`
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in CPS small repos project Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benedeki benedeki

Labels
spike Proof of concept, research and investigation tasks
Projects
CPS small repos project
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#178: Figure out a more natural way to work and identify flows AbsaOSS/atum-service
1 participant
@benedeki