Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
Boost.Serialization-based persistence currently lives on in the stack only in serialization of PropertyList and PropertySet, and in the pipelines I know of, only when saving Task metadata.
Several people have proposed switching to YAML-based persistence for these datasets, and (I believe) some partial implementations are underway.
Because Boost-based serialization is closely tied to daf_persistence code we're hoping to fully replace, I would like to transition to YAML for these datasets before we get to Gen3, and for Gen3 to not to support reading Task metadata persisted in that format (unlike all other Gen2 datasets, which we do intend to support reading via Gen3).
Attachments
Issue Links
- is triggering
-
DM-14503 Finish implementing YAML storage for PropertyList/PropertySet
- Done
-
DM-15082 Switch to YamlStorage instead of BoostStorage in all obs packages
- Done
-
DM-14504 Remove daf_persistence hooks in PropertySet, PropertyList, and afw objects
- Invalid
- relates to
-
DM-15593 daf_persistence segfaults on Princeton tiger2 cluster
- Done
-
RFC-222 Remove most formatter and boost::serialization code
- Implemented
-
DM-4927 ci_hsc doesn't produce readable processCcd_metadata
- Invalid
+1 That sounds like a great idea.