Skip to content

Commit 733a812

Browse files
authored
Corrected the meta data
Corrected the meta data
1 parent a3dbcdb commit 733a812

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/hdinsight/troubleshoot-sqoop.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Sqoop import/export command fails for some users in ESP clusters - Azure HDInsight
3-
description: 'Apache Sqoop import/export command fails with "Import Failed: java.io.IOException: The ownership on the staging directory /user/yourusername/.staging isn't as expected" error for some users in Azure HDInsight ESP cluster'
3+
description: Sqoop import/export command fails.
44
ms.service: hdinsight
55
ms.custom: devx-track-extended-java
66
ms.topic: troubleshooting
@@ -11,6 +11,7 @@ ms.date: 05/23/2024
1111

1212
This article describes a known issue and workaround when using Azure HDInsight ESP (Enterprise Security Pack) enabled clusters using ADLS Gen2 (ABFS) storage account.
1313

14+
'Apache Sqoop import/export command fails with "Import Failed: java.io.IOException: The ownership on the staging directory /user/yourusername/.staging isn't as expected" error for some users in Azure HDInsight ESP cluster'
1415
## Issue
1516

1617
When you run sqoop import/export command, it fails with the error for some users:

0 commit comments

Comments
 (0)