Skip to content

Commit 17ac51b

Browse files
Merge pull request #239649 from kevinjaku/main
Update known-issues.md
2 parents da73902 + 89e706b commit 17ac51b

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,7 @@ To learn more about Azure Synapse Analytics, see the [Azure Synapse Analytics Ov
2828
|Azure Synapse dedicated SQL pool|[Queries failing with Data Exfiltration Error](#queries-failing-with-data-exfiltration-error)|Has Workaround|
2929
|Azure Synapse Workspace|[Blob storage linked service with User Assigned Managed Identity (UAMI) is not getting listed](#blob-storage-linked-service-with-user-assigned-managed-identity-uami-is-not-getting-listed)|Has Workaround|
3030
|Azure Synapse Workspace|[Failed to delete Synapse workspace & Unable to delete virtual network](#failed-to-delete-synapse-workspace--unable-to-delete-virtual-network)|Has Workaround|
31+
|Azure Synapse Apache Spark pool|[Failed to write to SQL Dedicated Pool from Synapse Spark using Azure Synapse Dedicated SQL Pool Connector for Apache Spark when using notebooks in pipelines](#failed-to-write-to-sql-dedicated-pool-from-synapse-spark-using-azure-synapse-dedicated-sql-pool-connector-for-apache-spark-when-using-notebooks-in-pipelines)|Has Workaround|
3132

3233
## Azure Synapse Analytics serverless SQL pool active known issues summary
3334

@@ -95,6 +96,22 @@ Deleting a Synapse workspace fails with the error message:
9596

9697
**Workaround**: The problem can be mitigated by retrying the delete operation. The engineering team is aware of this behavior and working on a fix.
9798

99+
## Azure Synapse Analytics Apache Spark pool active known issues summary
100+
101+
The following are known issues with the Synapse Spark.
102+
103+
### Failed to write to SQL Dedicated Pool from Synapse Spark using Azure Synapse Dedicated SQL Pool Connector for Apache Spark when using notebooks in pipelines
104+
105+
While using Azure Synapse Dedicated SQL Pool Connector for Apache Spark to write Azure Synapse Dedicated pool using Notebooks in pipelines, we would see an error message:
106+
107+
`com.microsoft.spark.sqlanalytics.SQLAnalyticsConnectorException: COPY statement input file schema discovery failed: Cannot bulk load. The file does not exist or you don't have file access rights.`
108+
109+
**Workaround**: The engineering team is currently aware of this behavior and working on a fix. Following steps can be followed to work around the problem.
110+
- Set spark config through notebook:
111+
<br/>`spark.conf.set("spark.synapse.runAsMsi", "true")`
112+
- Or set spark config at [pool level](spark/apache-spark-azure-create-spark-configuration.md#create-an-apache-spark-configuration).
113+
114+
98115
## Recently Closed Known issues
99116

100117
|Synapse Component|Issue|Status|Date Resolved

0 commit comments

Comments
 (0)