cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
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
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
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.

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.