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: 

Apply Changes Statistics

Gilg
Contributor II

Hi Team,

I just wanted to know why APPLY_CHANGES do not show how many rows it got upserted in the graph? Is this something in the works in the future?

Cheers,

G

1 ACCEPTED SOLUTION

Accepted Solutions

Kaniz_Fatma
Community Manager
Community Manager

Hi @Gilg , The APPLY_CHANGES operation in Delta Lake does not provide metrics for the number of rows that were upserted in the graph. This limitation is mentioned in the Delta Lake documentation under the "Limitations" section.

Here are the relevant limitations mentioned in the documentation:- Metrics for the target table, such as the number of output rows, are not available.


- SCD type 2 updates will add a history row for every input row, even if no columns have changed.
- The target of the APPLY CHANGES INTO query or apply_changes function cannot be used as a source for a streaming table. A table that reads from the target of an APPLY CHANGES INTO query or apply_changes function must be a live table.
- Expectations are not supported in an APPLY CHANGES INTO query or apply_changes() function.

View solution in original post

1 REPLY 1

Kaniz_Fatma
Community Manager
Community Manager

Hi @Gilg , The APPLY_CHANGES operation in Delta Lake does not provide metrics for the number of rows that were upserted in the graph. This limitation is mentioned in the Delta Lake documentation under the "Limitations" section.

Here are the relevant limitations mentioned in the documentation:- Metrics for the target table, such as the number of output rows, are not available.


- SCD type 2 updates will add a history row for every input row, even if no columns have changed.
- The target of the APPLY CHANGES INTO query or apply_changes function cannot be used as a source for a streaming table. A table that reads from the target of an APPLY CHANGES INTO query or apply_changes function must be a live table.
- Expectations are not supported in an APPLY CHANGES INTO query or apply_changes() function.

Join 100K+ Data Experts: Register Now & Grow with Us!

Excited to expand your horizons with us? Click here to Register and begin your journey to success!

Already a member? Login and join your local regional user group! If there isn’t one near you, fill out this form and we’ll create one for you to join!