address comments

delta-io · Oct 31, 2023 · 33d20da · 33d20da
1 parent e267d17
commit 33d20da
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/PROTOCOL.md b/PROTOCOL.md
@@ -802,7 +802,8 @@ To support this feature:
  - To support Deletion Vectors, a table must have Reader Version 3 and Writer Version 7. A feature name `deletionVectors` must exist in the table's `readerFeatures` and `writerFeatures`.
 
 When supported:
- - A table's `add` and `remove` actions can optionally include a Deletion Vector (DV) that provides information about logically deleted rows, that are however still physically present in the underlying data file and must thus be skipped during processing. Readers must read the table considering the existence of DVs.
+ - A table may have a metadata property `delta.enableDeletionVectors` in the Delta schema set to `true`. Writers must set this property to write Deletion Vectors (DVs).
+ - A table's `add` and `remove` actions can optionally include a DV that provides information about logically deleted rows, that are however still physically present in the underlying data file and must thus be skipped during processing. Readers must read the table considering the existence of DVs, even when the `delta.enableDeletionVectors` table property is not set.
 
 DVs can be stored and accessed in different ways, indicated by the `storageType` field. The Delta protocol currently supports inline or on-disk storage, where the latter can be accessed either by a relative path derived from a UUID or an absolute path.