cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Delta table version protocol

noname123
New Contributor III

I do:

df.write.format("delta").mode("append").partitionBy("timestamp").option("mergeSchema", "true").save(destination)

If table doesn't exist, it creates new table with "minReaderVersion":3,"minWriterVersion":7.
Yesterday it was creating table with "minReaderVersion":1,"minWriterVersion":2. I changed nothing and now versions are different. Setting delta protocol version on cluster does nothing.
This causes breaking change to me because some tables are used by Azure Data Factory and it's not compatible.
1 ACCEPTED SOLUTION

Accepted Solutions

noname123
New Contributor III

Thanks for help.

Issue was caused by "Auto-Enable Deletion Vectors" setting. 

View solution in original post

2 REPLIES 2

noname123
New Contributor III

Thanks for help.

Issue was caused by "Auto-Enable Deletion Vectors" setting. 

AddBox45
New Contributor II

hello how did you fix this explicitly?how did you enable/disable the auto-enable deletion vectors setting to write again with minReaderVersion 1 and minWriterVersion 2?

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now