Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Story Points:2
-
Epic Link:
-
Team:Data Release Production
Description
(original description is no longer accurate; see comments)
Registry's provenance tables - execution, run, and quantum - can't currently be fully populated without having database updates. For example:
you can't insert a dataset until after its run has been inserted;you can't insert a run until you've inserted the execution it inherits its ID from;you can't insert an execution until after it's completed, because it has an end timestamp field.
Work through low-level use cases for these tables and ensure we can actually have all of their values when it's time to insert them, splitting up tables as necessary.
Michelle Gower, Christopher Stephens [X]: this ticket exists because I'm assuming updates are a problem. Please let me know if they aren't or if you have any expections/requirements/wisdom on when various provenance records should be inserted relative to the datasets they refer to.
Attachments
Issue Links
- is contained by
-
- Done
Activity
| Labels | gen3-middleware | gen2-deprecation-blocker gen3-middleware |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Summary | Rework Registry provenance tables to match insert order | Rework Registry provenance objects to match prototype |
| Description |
Registry's provenance tables - execution, run, and quantum - can't currently be fully populated without having database updates. For example:
* you can't insert a dataset until after its run has been inserted; * you can't insert a run until you've inserted the execution it inherits its ID from; * you can't insert an execution until after it's completed, because it has an end timestamp field. Work through low-level use cases for these tables and ensure we can actually have all of their values when it's time to insert them, splitting up tables as necessary. [~mgower], [~cs2018]: this ticket exists because I'm assuming updates are a problem. Please let me know if they aren't or if you have any expections/requirements/wisdom on when various provenance records should be inserted relative to the datasets they refer to. |
(original description is no longer accurate; see comments)
-Registry's provenance tables - execution, run, and quantum - can't currently be fully populated without having database updates. For example:- * -you can't insert a dataset until after its run has been inserted;- * -you can't insert a run until you've inserted the execution it inherits its ID from;- * -you can't insert an execution until after it's completed, because it has an end timestamp field.- -Work through low-level use cases for these tables and ensure we can actually have all of their values when it's time to insert them, splitting up tables as necessary.- [~mgower]-,- [~cs2018]-: this ticket exists because I'm assuming updates are a problem. Please let me know if they aren't or if you have any expections/requirements/wisdom on when various provenance records should be inserted relative to the datasets they refer to.- |
| Story Points | 3 | 2 |
| Reviewers | Mikolaj Kowalik [ mkowalik ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
Mikolaj Kowalik
made changes -
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |