THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Definition
Type that determines how a def~commit will be stored and handled relative to its application to the target def~dataset.data will be laid out as file and stored, inside a def~table.
#todo verify
Following table summarizes the trade-offs between these two storage table types
| Trade-off | def~copy-on-write (COW) | def~merge-on-read (MOR) | ||
|---|---|---|---|---|
| Data Latency | Higher | Lower | ||
| Update cost (I/O) | Higher (rewrite entire def~dataset def~table parquet) | Lower (append to `delta log`)Parquet File Size | Smaller (high update(I/0) cost) | Larger (low update cost) |
| Write Amplification | Higher | Lower (depending on compaction strategy to the def~dataset parquet def~table parquet) | ||
| Query/Read Amplification | Lower/Zero | Higher (merging base and deltas on the fly) |