Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Labels:
-
Story Points:12
-
Epic Link:
-
Sprint:DB_S21_12
-
Team:Data Access and Database
-
Urgent?:No
Description
Syncing registries from different sources (such as the lightweight registry from workflows) will be simplified significantly if we switch from autoincrementing integers to UUIDs for our datasets.
Some things to consider:
- Where are UUIDs calculated? By Registry?
- Should we allow UUIDs to be calculated from a datasetRef (dataset type / dataId and run name). This could be an alternative implementation of
DM-21794, allowing raw data to have predictable IDs. - Should we allow an external source for UUID?
- Is there a case for datastore to allocate IDs itself which can then be used by registry?
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Syncing registries from different sources (such as the lightweight registry from workflows) will be simplified significantly if we switch from autoincrementing integers to UUIDs for our datasets.
Some things to consider: * Where are UUIDs calculated? By Registry? * Should we allow UUIDs to be calculated from a dataId and collection name. This could be an alternative implementation of * Is there a case for datastore to allocate IDs itself which can then be used by registry? |
Syncing registries from different sources (such as the lightweight registry from workflows) will be simplified significantly if we switch from autoincrementing integers to UUIDs for our datasets.
Some things to consider: * Where are UUIDs calculated? By Registry? * Should we allow UUIDs to be calculated from a datasetRef (dataset type / dataId and run name). This could be an alternative implementation of * Should we allow an external source for UUID? * Is there a case for datastore to allocate IDs itself which can then be used by registry? |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Remote Link | This issue links to "DMTN-099 (Web Link)" [ 27936 ] |
Epic Link |
|
|
Sprint | DB_S21_12 [ 1065 ] | |
Labels | gen3-middleware |
Attachment | DM-29196 datasets insert time sqlite.png [ 48516 ] | |
Attachment | DM-29196 datasets insert time postgres.png [ 48517 ] |
Attachment |
|
Attachment |
|
Attachment | DM-29196 datasets insert time postgres.png [ 48520 ] | |
Attachment | DM-29196 datasets insert time sqlite.png [ 48521 ] |
Remote Link | This issue links to "Script used for testing INSERT performance (Web Link)" [ 27943 ] |
Attachment | DM-29196 timing datasets methods uuid.png [ 48566 ] | |
Attachment | DM-29196 timing datasets methods original.png [ 48567 ] | |
Attachment | DM-29196 datasets schema uuid.png [ 48568 ] |
Watchers | Andy Salnikov, Jim Bosch, Michelle Gower, Tim Jenness [ Andy Salnikov, Jim Bosch, Michelle Gower, Tim Jenness ] | Andy Salnikov, Brian Yanny, Jim Bosch, Michelle Gower, Tim Jenness [ Andy Salnikov, Brian Yanny, Jim Bosch, Michelle Gower, Tim Jenness ] |
Summary | Use UUIDs are dataset_ids in registry | Use UUIDs as dataset_ids in registry |
Reviewers | Jim Bosch [ jbosch ] | |
Status | In Progress [ 3 ] | In Review [ 10004 ] |
Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Resolution | Done [ 10000 ] | |
Status | Reviewed [ 10101 ] | Done [ 10002 ] |