Yes... I know... but....
The cluster is not administered by me
On Mié., Ago. 9, 2017 at 13:46, Gourav Sengupta wrote:
Just out of sheer curiosity - why are you using SPARK 1.6? Since then SPARK has
made significant advancement and improvement, why not take advantage of that?
On Wed, Aug 9, 2017 at 10:41 AM, toletum wrote:
I fixed it
On Mié., Ago. 9, 2017 at 11:22, Matteo Cossu wrote:
try to use these options when starting Spark:
--conf "spark.driver.userClassPathFirst=true" --conf
In this way you will be sure that the executor and the driver of Spark will use
the classpath you define.
On 5 August 2017 at 23:04, toletum wrote:
I'm trying to connect Spark to Hive.
Hive uses Derby Server for metastore_db.
JDBC connect string for a JDBC metastore
Driver class name for a JDBC metastore
I have copied to $SPARK_HOME/lib derby.jar, derbyclient.jar, derbytools.jar
Added to CLASSPATH the 3 jars too
But spark-sql saids:
The specified datastore driver ("org.apache.derby.jdbc.ClientDriver") was not
found in the CLASSPATH. Please check your CLASSPATH specification, and the name
of the driver.
java finds the class
Error: Main method not found in class org.apache.derby.jdbc.ClientDriver,
please define the main method as:
public static void main(String args)
or a JavaFX application class must extend javafx.application.Application
It seems Spark can't find the driver