Skip to content

Commit f884daa

Browse files
Merge pull request #259359 from v-akarnase/patch-14
Update apache-spark-troubleshoot-job-fails-noclassdeffounderror.md
2 parents 6260f93 + b8cf838 commit f884daa

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/hdinsight/spark/apache-spark-troubleshoot-job-fails-noclassdeffounderror.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: NoClassDefFoundError - Apache Spark with Apache Kafka data in Azure HDIns
33
description: Apache Spark streaming job that reads data from an Apache Kafka cluster fails with a NoClassDefFoundError in Azure HDInsight
44
ms.service: hdinsight
55
ms.topic: troubleshooting
6-
ms.date: 10/07/2022
6+
ms.date: 11/23/2023
77
---
88

99
# Apache Spark streaming job that reads Apache Kafka data fails with NoClassDefFoundError in HDInsight
@@ -24,9 +24,9 @@ Stack trace: ExitCodeException exitCode=50:
2424

2525
## Cause
2626

27-
This error can be caused by specifying a version of the `spark-streaming-kafka` jar file that is different than the version of the Kafka cluster you are running.
27+
This error can be caused by specifying a version of the `spark-streaming-kafka` jar file that is different than the version of the Kafka cluster you're running.
2828

29-
For example, if you are running a Kafka cluster version 0.10.1, the following command will result in an error:
29+
For example, if you're running a Kafka cluster version 0.10.1, the following command results in an error:
3030

3131
```
3232
spark-submit \
@@ -38,7 +38,7 @@ spark-submit \
3838

3939
## Resolution
4040

41-
Use the Spark-submit command with the `–packages` option, and ensure that the version of the spark-streaming-kafka jar file is the same as the version of the Kafka cluster that you are running.
41+
Use the `Spark-submit` command with the `–packages` option, and ensure that the version of the spark-streaming-kafka jar file is the same as the version of the Kafka cluster that you are running.
4242

4343
## Next steps
4444

0 commit comments

Comments
 (0)