Skip to content

Commit 89e706b

Browse files
authored
Update known-issues.md
1 parent 1c769fd commit 89e706b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/synapse-analytics/known-issues.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,14 +102,14 @@ The following are known issues with the Synapse Spark.
102102

103103
### 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
104104

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 as below:
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:
106106

107107
`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.`
108108

109109
**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 below spark config through notebook:
110+
- Set spark config through notebook:
111111
<br/>`spark.conf.set("spark.synapse.runAsMsi", "true")`
112-
- Or set above spark config at [pool level](spark/apache-spark-azure-create-spark-configuration#create-an-apache-spark-configuration).
112+
- Or set spark config at [pool level](spark/apache-spark-azure-create-spark-configuration.md#create-an-apache-spark-configuration).
113113

114114

115115
## Recently Closed Known issues

0 commit comments

Comments
 (0)