Skip to content

Commit c974a4e

Browse files
authored
Merge pull request #174097 from Clare-Zheng82/0930-Add_new_TSG_to_Activity_Databricks
Add one new TSG to Activities-Azure Databricks section
2 parents 903b121 + adb8e76 commit c974a4e

File tree

3 files changed

+15
-1
lines changed

3 files changed

+15
-1
lines changed

articles/data-factory/data-factory-troubleshoot-guide.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: data-factory
77
ms.subservice: troubleshooting
88
ms.custom: synapse
99
ms.topic: troubleshooting
10-
ms.date: 09/26/2021
10+
ms.date: 09/30/2021
1111
ms.author: abnarain
1212
---
1313

@@ -137,6 +137,20 @@ For connector issues such as an encounter error using the copy activity, refer t
137137

138138
- **Recommendation**: If you're using a self-hosted integration runtime, make sure that the network connection is reliable from the integration runtime nodes. If you're using Azure integration runtime, retry usually works.
139139

140+
### The Boolean run output starts coming as string instead of expected int
141+
142+
- **Symptoms**: Your Boolean run output starts coming as string (for example, `"0"` or `"1"`) instead of expected int (for example, `0` or `1`).
143+
144+
:::image type="content" source="media/data-factory-troubleshoot-guide/databricks-pipeline.png" alt-text="Screenshot of the Databricks pipeline.":::
145+
146+
You noticed this change on September 28, 2021 at around 9 AM IST when your pipeline relying on this output started failing. No change was made on the pipeline, and the Boolean output had been coming as expected before the failure.
147+
148+
:::image type="content" source="media/data-factory-troubleshoot-guide/old-and-new-output.png" alt-text="Screenshot of the difference in the output.":::
149+
150+
- **Cause**: This issue is caused by a recent change, which is by design. After the change, if the result is a number that starts with zero, Azure Data Factory will convert the number to the octal value, which is a bug. This number is always 0 or 1, which never caused issues before the change. So to fix the octal conversion, the string output is passed from the Notebook run as is.
151+
152+
- **Recommendation**: Change the **if** condition to something like `if(value=="0")`.
153+
140154
## Azure Data Lake Analytics
141155

142156
The following table applies to U-SQL.
147 KB
Loading
90.9 KB
Loading

0 commit comments

Comments
 (0)