Expand description
Actions are the fundamental unit of work in Delta Lake. Each action performs a single atomic
operation on the state of a Delta table. Actions are stored in the _delta_log directory of a
Delta table in JSON format. The log is a time series of actions that represent all the changes
made to a table.
Structs§
- Defines an add action
- Delta AddCDCFile action that describes a parquet CDC data file.
- This action is only allowed in checkpoints following V2 spec. It describes the details about the checkpoint.
- The commitInfo is a fairly flexible action within the delta specification, where arbitrary data can be stored. However the reference implementation as well as delta-rs store useful information that may for instance allow us to be more permissive in commit conflict resolution.
- Defines a deletion vector
- The domain metadata action contains a configuration (string) for a named metadata domain
- Defines a file format used in table
- An invariant for a column that is enforced on all writes to a Delta table.
- Defines a metadata action
- Defines a protocol action
- Represents a tombstone (deleted file) in the Delta log.
- The sidecar action references a sidecar file which provides some of the checkpoint’s file actions. This action is only allowed in checkpoints following V2 spec.
- A struct is used to represent both the top-level schema of the table as well as struct columns that contain nested columns.
- Action used by streaming systems to track progress using application-specific versions to enable idempotency.
Enums§
- The type of action that was performed on the table
- The isolation level applied during transaction
- Features table readers can support as well as let users know what is supported
- Storage type of deletion vector
- High level table features
- Features table writers can support as well as let users know what is supported
Traits§
- Trait to add convenince functions to struct type
Type Aliases§
- Type alias for a top level schema
- Schema reference type