Home
Overview
Fundamentals
Glossary
Cheatsheet
API Reference
Quick Recipes
Deep Dive
Common Pitfalls and Gotchas
Persistent Storage
Metadata about a revision of a DataSliceManager.
A revision gets created for each successful write operation, i.e. an operation
that can mutate the data and/or schema managed by the manager.
Revision metadata should ideally be represented in a format that can render in
a human-readable way out of the box. The reason is that the primary use case
of the metadata is to surface history information to users in interactive
sessions or during debugging. So as a rule of thumb, the data should be
organized in a way that is easy to consume. E.g. it should be flattened, not
(deeply) nested, and timestamps and DataSlicePath are presented as
human-readable strings.
RevisionMetadata.__init__(self, description: str, timestamp: str) -> NoneInitialize self. See help(type(self)) for accurate signature.