New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"java.lang.VerifyError: Bad return type" runnig spark-solr in Scala on Cloudera-5.5 #36
Comments
I was importing solr-core 4.10.3 but spark-solr has a dependency on Solr 5.3.1 that I was not aware of. This means it is not compatible with the current cloudera version (4.10.3) |
4.10.3 is an old version of Solr. The |
Hello, I'm having the same error with Apache Solr 6.0.0. I tried it with Spark-Solr 2.0.0 and also with master branch with Solr version set to the latest version too. I'm using CDH 5.7 and Spark 1.6.0. Here is the stacktrace:
Thanks in advance. |
@hakanilter The master branch and 2.0.x are tested only with 5.5.1. Once the bug release (6.0.1) is out, I will update the master and re-compile, fix any bugs. Does CDH 5.7 ship with stock 6.0.0 Solr ? |
@kiranchitturi CDH 5.7 comes with Solr 4.3.10, I run Solr 6.0.0 with docker. Thanks. |
Download the following jars (just google for it) and copy them to your %hadoop_home%\share\hadoop\common\lib folder. httpclient-4.4.1.jar Refer to this link: http://prasi82.blogspot.in/2015/11/spark-solr-integration-on-windows.html |
Apologies if this is an error in my setup rather than an issue with the code, but I am not sure myself.
I am trying to ingest documents into Solr from a Spark Streaming job in Scala.
This is the Solr related code block:
When I run this via spark-submit the job fails straight away because of a java.lang.VerifyError. I presume I am mismatching versions of code somewhere here to get the following error:
From what I can tell the SystemDefaultHttpClient extends from CloseableHttpClient so I don't see why this fails. Does anyone have an idea what is wrong?
I am using:
Dependencies from build.sbt:
Thanks,
Donal
The text was updated successfully, but these errors were encountered: