Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler
-
Story Points:1
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Getting the quantum database representation stable and future-proof requires more thought than we want to put into it before gen2 deprecation, so this ticket is a near-term replacement for DM-24613, which we'll pick up again later. See also https://lsstc.slack.com/archives/C2JPT1KB7/p1591284060371700
Preliminary plan is to remove the quantum and dataset_consumer tables, along with the dataset.quantum_id column. It'll be easier to add those back in than alter them to match what we do in the future.
Attachments
Issue Links
- relates to
-
DM-24613 Move Quantum tables into manager/storage hierarchy
- In Progress
This is purely code removal. The Quantum object itself is preserved because we of course use that in other packages, but we aren't using the tables right now at all, and as per ticket description we're going to remove them now so it's easier to add fixed versions (rather than deal with altering broken ones) later.
PR is https://github.com/lsst/daf_butler/pull/303; I think this should just be daf_butler, but Jenkins is running to tell me if I'm wrong about that.