[Feature Request] Support `failOnDataLoss` property for Delta source schema tracking

[jackierwzhang]

Feature request

Which Delta project/connector is this regarding?

• [x] Spark
• [ ] Standalone
• [ ] Flink
• [ ] Kernel
• [ ] Other (fill in here)

Overview

We currently support schemaTrackingLocation (doc) that allows Delta streaming source to track additive and non-additive schema changes during streaming from a Delta table.

However, if failOnDataLoss reader option is used and there's a gap in the data log (e.g. due to log out of retention period), schemaTrackingLocation usage will be blocked.

There maybe better mechanisms to tackle this scenario, such as introducing an option to reinitialize the schema tracking log with the next available schema at that time.

Motivation

This allows the schemaTrackingLocation option be used with failOnDataLoss.

Further details

Willingness to contribute

The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

• [ ] Yes. I can contribute this feature independently.
• [ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
• [ ] No. I cannot contribute this feature at this time.