What causes DELTA_PROTOCOL_VERSION_NOT_SUPPORTED?

The table was written by a newer version of Databricks Runtime or Delta Lake that uses a higher protocol version. A Delta feature (e.g., column mapping, deletion vectors, row tracking) was enabled that requires a higher protocol version. An older Delta Lake library (e.g., delta-spark 2.x) is being used to read a table written with delta-spark 3.x. The minReaderVersion or minWriterVersion in the table properties exceeds the client's capabilities

How do I fix DELTA_PROTOCOL_VERSION_NOT_SUPPORTED?

Step 1: Run SELECT * FROM table.history LIMIT 1 or DESCRIBE DETAIL table_name to see the current minReaderVersion and minWriterVersion.. Step 2: Upgrade the Databricks Runtime or Delta Lake library to a version that supports the required protocol version.. Step 3: If a specific Delta feature caused the version bump, evaluate whether it can be disabled on this table.. Step 4: For external readers (e.g., Power BI via XMLA), ensure the connector library is up to date.. Step 5: Avoid downgrading table protocol versions — not all features can be safely rolled back.

High severityconfiguration

Power BI Refresh Error:
DELTA_PROTOCOL_VERSION_NOT_SUPPORTED

What does this error mean?

The Delta Lake reader or writer version required by the table exceeds what the current client library supports, preventing reads or writes.

Common causes

1The table was written by a newer version of Databricks Runtime or Delta Lake that uses a higher protocol version
2A Delta feature (e.g., column mapping, deletion vectors, row tracking) was enabled that requires a higher protocol version
3An older Delta Lake library (e.g., delta-spark 2.x) is being used to read a table written with delta-spark 3.x
4The minReaderVersion or minWriterVersion in the table properties exceeds the client's capabilities

How to fix it

1Step 1: Run SELECT * FROM table.history LIMIT 1 or DESCRIBE DETAIL table_name to see the current minReaderVersion and minWriterVersion.
2Step 2: Upgrade the Databricks Runtime or Delta Lake library to a version that supports the required protocol version.
3Step 3: If a specific Delta feature caused the version bump, evaluate whether it can be disabled on this table.
4Step 4: For external readers (e.g., Power BI via XMLA), ensure the connector library is up to date.
5Step 5: Avoid downgrading table protocol versions — not all features can be safely rolled back.

Frequently asked questions

Which Delta Lake features increase the protocol version?

Column mapping (minReaderVersion 2), deletion vectors (minReaderVersion 3), row tracking and liquid clustering (minReaderVersion 3, minWriterVersion 7), and change data feed (minWriterVersion 4) all bump the protocol version.

Can I downgrade a Delta table's protocol version?

Generally no — once a table's protocol version is bumped by enabling a feature, it cannot be downgraded without recreating the table. Plan upgrades carefully.