如何解决 java.lang.NoSuchMethodError org.apache.spark.ml.util.SchemaUtils$.checkColumnType答案

【问题标题】：How to resolve java.lang.NoSuchMethodError org.apache.spark.ml.util.SchemaUtils$.checkColumnType如何解决 java.lang.NoSuchMethodError org.apache.spark.ml.util.SchemaUtils$.checkColumnType
【发布时间】：2016-02-05 08:51:27
【问题描述】：

我正在尝试运行此处提供的 CountVectorizerDemo 程序：

https://github.com/apache/spark/blob/master/examples/src/main/java/org/apache/spark/examples/ml/JavaCountVectorizerExample.java

我收到以下错误，不知道是什么问题。

Exception in thread "main" java.lang.NoSuchMethodError: org.apache.spark.ml.util.SchemaUtils$.checkColumnType$default$4()Ljava/lang/String;
    at org.apache.spark.ml.feature.CountVectorizerParams$class.validateAndTransformSchema(CountVectorizer.scala:71)
    at org.apache.spark.ml.feature.CountVectorizer.validateAndTransformSchema(CountVectorizer.scala:107)
    at org.apache.spark.ml.feature.CountVectorizer.transformSchema(CountVectorizer.scala:168)
    at org.apache.spark.ml.PipelineStage.transformSchema(Pipeline.scala:59)
    at org.apache.spark.ml.feature.CountVectorizer.fit(CountVectorizer.scala:130)
    at com.bah.ossem.spark.topic.CountVectorizerDemo.main(CountVectorizerDemo.java:42)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:664)
    at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:169)
    at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:192)
    at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:111)
    at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)

【问题讨论】：

标签： java exception apache-spark apache-spark-mllib

【解决方案1】：

问题是我的集群使用的是 Spark 核心 1.4，但我的应用程序使用的是 Spark 核心 1.5.1 和 MLlib 1.5.1。我将我的 AWS 集群更新到 Spark 1.5.1 并解决了这个问题。

【讨论】：