Skip to content

schema evolution for ROOT I/O #48

@chenel

Description

@chenel

As there are more and more uses for CAFs, changes to the format become increasingly disruptive, since CAFs made with differing versions of duneanaobj have to be read back with a version that's compatible with their structure.

ROOT's "schema evolution" concept can be used to deal with many of these cases. We should begin using it to help reduce the number of "breaking changes" that adjustments to the storage format cause.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions