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

Invalid executions #120

Open
stuartmcalpine opened this issue Apr 29, 2024 · 1 comment
Open

Invalid executions #120

stuartmcalpine opened this issue Apr 29, 2024 · 1 comment
Assignees
@JoanneBogart
Labels
question Further information is requested

Comments

@stuartmcalpine
Copy link
Collaborator

If a dataset fails during copying the data, it has a left over database entry, but it remains "invalid".

However if the execution for that dataset is the default fabricated one, it gets created first, so there will be a left over execution. Should executions then also have a valid/invalid status?
@stuartmcalpine stuartmcalpine added the question Further information is requested label Apr 29, 2024
@JoanneBogart
Copy link
Collaborator

I think that's the best option.
This is one case where I would consider deleting the execution entry, but that doesn't help - one still has the dataset entry which needs to refer to some execution.
So yes, let's add a status field for executions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JoanneBogart JoanneBogart

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JoanneBogart @stuartmcalpine