Data shares update: Deprecating Delta Sharing CDF feature

[#1]

Hi Community,

We want to inform you about the deprecation of the Delta Sharing Change Data Feed (CDF) feature.

What is Delta Sharing CDF?

The Delta Sharing CDF feature allows Delta tables to track row-level changes between versions of a Delta table. When enabled, it records “change events” for all data written into the table, including whether a row was inserted, deleted, or updated.

Why are we deprecating it?

After careful consideration, we've decided to deprecate the Delta CDF feature as part of overarching efforts to better support all of our customers. We've ensured that the deprecation has minimal disruptions for customers currently using it.

Deprecation timeline

We'll deprecate this feature on November 17th, 2025. To assist with the deprecation, we’re directly contacting all customers who are impacted by this or are currently using this feature.

What's the recommended alternative?

For incremental data loads, we recommend using the row_refreshed_at column to filter records that have changed since your last load. For example:

SELECT * FROM jira_issue
WHERE row_refreshed_at > {{previous_run_timestamp}}

While this approach may require more data computation than CDF, the impact will be minimal due to predicate hints and Parquet header pruning.

If you have any questions or concerns about this change, you can either contact support or comment on this post.

[Josh]

Hi @Mehak Bokhari .

Thank you for the heads-up.

The timeline is a bit aggressive (less than 3 weeks' notice) and it's not clear what the actual value of the deprecation is since the statement is so broad and generic:

After careful consideration, we've decided to deprecate the Delta CDF feature as part of overarching efforts to better support all of our customers.

[Mehak Bokhari]

Hi @Josh

Thank you for this feedback and completely understand that the 3 week notice may be quite short and our team took that into consideration. Prior to this post, we have reached out directly to all customers that have been using this feature to give them more notice and assist with any work that needs to be done to assist them to switch to the alternative option. 

In regards to the value of deprecation, this is a part of a broader plan to improve our platform for an increasing cohort of customers. Ultimately we want to unlock better performance in the future.

Hopefully this gives more clarity to the deprecation.