From 65c0f4dcca555afbd7fa4f2a15442229791be531 Mon Sep 17 00:00:00 2001
From: basland <66687590+basland@users.noreply.github.com>
Date: Thu, 23 Oct 2025 08:34:16 +0200
Subject: [PATCH 1/2] Update delta-optimization-and-v-order.md

Added prerequisite for the ALTER command when setting V-Order on a delta table
---
 docs/data-engineering/delta-optimization-and-v-order.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/data-engineering/delta-optimization-and-v-order.md b/docs/data-engineering/delta-optimization-and-v-order.md
index 0df9f0c508..41c94ec280 100644
--- a/docs/data-engineering/delta-optimization-and-v-order.md
+++ b/docs/data-engineering/delta-optimization-and-v-order.md
@@ -164,7 +164,8 @@ CREATE TABLE person (id INT, name STRING, age INT) USING parquet TBLPROPERTIES("
 > [!IMPORTANT]
 > When the table property is set to true, INSERT, UPDATE, and MERGE commands behave as expected and perform the write-time optimization. If the V-Order session configuration is set to true or the spark.write enables it, then the writes are V-Order even if the TBLPROPERTIES is set to false.
 
-Enable or disable V-Order by altering the table property:
+
+Enable or disable V-Order by altering the table property (note that you need to have 'spark.databricks.delta.allowArbitraryProperties.enabled' set to 'true'): 
 
 ```sql
 %%sql 

From 37e584491dba9ad890cad438ba368a762b8e6d7c Mon Sep 17 00:00:00 2001
From: basland <66687590+basland@users.noreply.github.com>
Date: Thu, 23 Oct 2025 16:41:50 +0200
Subject: [PATCH 2/2] Update
 docs/data-engineering/delta-optimization-and-v-order.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
---
 docs/data-engineering/delta-optimization-and-v-order.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/data-engineering/delta-optimization-and-v-order.md b/docs/data-engineering/delta-optimization-and-v-order.md
index 41c94ec280..02602eb51c 100644
--- a/docs/data-engineering/delta-optimization-and-v-order.md
+++ b/docs/data-engineering/delta-optimization-and-v-order.md
@@ -165,8 +165,10 @@ CREATE TABLE person (id INT, name STRING, age INT) USING parquet TBLPROPERTIES("
 > When the table property is set to true, INSERT, UPDATE, and MERGE commands behave as expected and perform the write-time optimization. If the V-Order session configuration is set to true or the spark.write enables it, then the writes are V-Order even if the TBLPROPERTIES is set to false.
 
 
-Enable or disable V-Order by altering the table property (note that you need to have 'spark.databricks.delta.allowArbitraryProperties.enabled' set to 'true'): 
+Enable or disable V-Order by altering the table property:
 
+> [!NOTE]
+> You need to have 'spark.databricks.delta.allowArbitraryProperties.enabled' set to 'true'.
 ```sql
 %%sql 
 ALTER TABLE person SET TBLPROPERTIES("delta.parquet.vorder.default" = "true");