Uploaded image for project: 'Request For Comments'
  1. Request For Comments
  2. RFC-482

Retire use of Boost.Serialization persistence before Gen3 Butler transition

    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

          Container Issues

            Issue Links

              Activity

                People

                • Assignee:
                  jbosch Jim Bosch
                  Reporter:
                  jbosch Jim Bosch
                  Watchers:
                  Colin Slater, Jim Bosch, John Parejko, John Swinbank, Kian-Tat Lim, Tim Jenness
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Planned End:

                    Summary Panel