Forum Discussion
undefined
Hi Sureshmannem ,
Thank you for the follow-up. We would be happy to assist you!
Upon my knowledge, this is a known limitation when using Copy Activity with Delta Lake tables in Fabric , the “Import Schema” feature is not supported, which explains the inconsistent behavior you are seeing with locked or missing column mappings. This is documented in the official guidance here: Copy data from/to Lakehouse – Limitations.
For more context, you may also refer to the link: Data Factory limitations in Fabric.
Hope this helps.
Thank you.
Hi Sureshmannem ,
Thank you for reaching out to us on Microsoft Fabric Community Forum!
This is a known limitation, Delta may need the schema to be set up ahead of time or mapped manually. The best workaround is to define the mappings yourself or make sure the table already exists with the right structure.
Refer the below solved thread and the document for more information:
https://community.fabric.microsoft.com/t5/Data-Engineering/Copy-data-activity-creates-no-proper-delta-table-with-schema-in/m-p/4387754
https://learn.microsoft.com/en-us/fabric/data-factory/connector-lakehouse-copy-activity#limitations
https://learn.microsoft.com/en-us/azure/data-factory/connector-azure-databricks-delta-lake?tabs=data-factory
Hope this helps.If so,give us kudos and consider accepting it as solution.
Thank you.
Regards,
Pallavi.