Forum Discussion
DeltaNotSupportedAction - Fabric Lakehouse
I have an ADF pipeline with a copy activity that fetches data from Salesforce (nearly 8 tables) and pushes it to Fabric Lakehouse with the overwrite option. However, during the pipeline execution, two of the tables failed due to an error:
Failure happened on the 'Sink' side. ErrorCode=DeltaNotSupportedAction,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The supported Delta actions in Delta log file are Metadata, Add, Remove, CDC, Transaction, Protocol and CommitInfo.,Source=Microsoft.DataTransfer.ClientLibrary,'
The last delta log file written was as shown below:
HI Kanna123
Thank you for reaching out to the Microsoft Fabric Community Forum.
The solution provided by nilendraFabric is accurate. Additionally, here are a few more points that may be helpful.
The error occurs because the Delta log file contains actions not supported by the Delta Lake implementation.
These could include:
- Corrupted entries caused by interrupted operations .
- Concurrent updates that cause conflicting log entries.
- Invalid or unsupported schema updates during data write.
- Unexpected file states in the storage layer.
1. Check the Delta Log Files
- Inspect the Delta log files (_delta_log directory) to identify the unsupported action causing the issue.
2. Identify the Source of the Unsupported Action
- Ensure that the source data or transformation logic is not introducing unsupported actions into the Delta log.
3. Validate the Data Ingestion Process
- Review the data ingestion pipeline or job that writes to the Delta table.
- Ensure that the pipeline uses a compatible version of Delta Lake and that the operations being performed are supported.
4. Check for Delta Lake Version Compatibility
- Ensure that the version of Delta Lake being used is compatible with the actions being performed. If you are using an older version of Delta Lake, consider upgrading to the latest version, as newer versions may support additional actions or have bug fixes.
If my response has resolved your query, please mark it as the Accepted Solution to help others. Additionally, I would appreciate a 'Kudos' if you found my response helpful.
Thank you!
4 Replies
Hello Kanna123
seems like schema changed between 2 loads
Schema Mismatch or Metadata Issues:
• A mismatch between the source data schema and the Delta table schema could lead to metadata-related errors.
• Solution: Verify that the source data schema matches the Delta table schemacould you please check it once. Else drop the table in lakehouse and rerun the pipeline.
sometimes metadata for delta table cause these issues and they are tough to resolve. Best option is to recreate the table
thanks
hi nilendraFabric
I dropped and recreated the table to resolve the issue and ensure the pipeline runs smoothly. It is now working fine. The source table does not seem to have any schema changes; I verified the Delta logs before deleting the table and after recreating it. This is the second occurrence of the issue, and I am looking to identify the root cause and find a solution to fix itSo after recreating the table and multiple run it failed again?
please share your merge logic here
HI Kanna123
Thank you for reaching out to the Microsoft Fabric Community Forum.
The solution provided by nilendraFabric is accurate. Additionally, here are a few more points that may be helpful.
The error occurs because the Delta log file contains actions not supported by the Delta Lake implementation.
These could include:
- Corrupted entries caused by interrupted operations .
- Concurrent updates that cause conflicting log entries.
- Invalid or unsupported schema updates during data write.
- Unexpected file states in the storage layer.
1. Check the Delta Log Files
- Inspect the Delta log files (_delta_log directory) to identify the unsupported action causing the issue.
2. Identify the Source of the Unsupported Action
- Ensure that the source data or transformation logic is not introducing unsupported actions into the Delta log.
3. Validate the Data Ingestion Process
- Review the data ingestion pipeline or job that writes to the Delta table.
- Ensure that the pipeline uses a compatible version of Delta Lake and that the operations being performed are supported.
4. Check for Delta Lake Version Compatibility
- Ensure that the version of Delta Lake being used is compatible with the actions being performed. If you are using an older version of Delta Lake, consider upgrading to the latest version, as newer versions may support additional actions or have bug fixes.
If my response has resolved your query, please mark it as the Accepted Solution to help others. Additionally, I would appreciate a 'Kudos' if you found my response helpful.
Thank you!
