This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 28.000000000000004%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAP%3C/text%3E%3C/svg%3E)
Hi, I am using synapse pipeline and sink component is writing files in a stage location. It is been able to successfully write the files but I throws the following error message.
Error: {"StatusCode":"DFExecutorUserError","Message":"Job failed due to reason: at Sink 'QcRxFactData': org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: This operation is not permitted on a non-empty directory.","Details":"at Sink 'QcRxFactData': org.apache.hadoop.fs.azure.AzureException: com.microsoft.azure.storage.StorageException: This operation is not permitted on a non-empty directory."}
Any help will be highly appreciated.
Regards,
Arindam Pandit
Hello @arindam.pandit ,
Welcome to the Microsoft Q&A platform.
Was the write operation was being performed in ADLS Gen2 with hierarchical namespace and using the same container as input and output?
In case using the same container, I would suggest to separate input and output containers to facilitate and isolate read operations from write operations.
It was in ADL Gen 2 with hierarchical namespace. Sink component is dumping the file from source container to sink container in stage folder. source and sink are two different container in the same storage account.
It was resolved. The problem was in connector. We were using DLG2 but while creating the Linked Service, as connector we choose Blob Connector. Replacing the connector solved the issue.
Hello @arindam.pandit ,
Glad to know that your issue has resolved. You can accept it as an answer. And thanks for sharing the solution, which might be beneficial to other community members reading this thread.