You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spark.apache.org by JaeSung Jun <ja...@gmail.com> on 2015/07/30 04:02:20 UTC

unit test failure for hive query

Hi,
I'm working on custom sql processing on top of Spark-SQL, and i'm upgrading
it along with spark 1.4.1.
I've got an error regarding multiple test suites access hive meta store at
the same time like :

 Cause: org.apache.derby.impl.jdbc.EmbedSQLException: Another instance of
Derby may have already booted the database /Users/~~~/metastore_db.

  at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
Source)

  at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
Source)

  at
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
Source)

  at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)

  at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)

  at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)

  at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)

  at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)

  at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)

  at org.apache.derby.jdbc.Driver20.connect(Unknown Source)


It was okay with spark 1.3.0.

Any idea to fist this?


thanks in advance.

Jason

Re: unit test failure for hive query

Posted by Michael Armbrust <mi...@databricks.com>.

I'd suggest using org.apache.spark.sql.hive.test.TestHive as the context in
unit tests.  It takes care of creating separate directories for each
invocation automatically.

On Wed, Jul 29, 2015 at 7:02 PM, JaeSung Jun <ja...@gmail.com> wrote:

> Hi,
> I'm working on custom sql processing on top of Spark-SQL, and i'm
> upgrading it along with spark 1.4.1.
> I've got an error regarding multiple test suites access hive meta store at
> the same time like :
>
>  Cause: org.apache.derby.impl.jdbc.EmbedSQLException: Another instance of
> Derby may have already booted the database /Users/~~~/metastore_db.
>
>   at
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
>
>   at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
> Source)
>
>   at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
>
>   at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
>
>   at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown
> Source)
>
>   at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
>
>   at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
>
>   at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
>
>   at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
>
>   at org.apache.derby.jdbc.Driver20.connect(Unknown Source)
>
>
> It was okay with spark 1.3.0.
>
> Any idea to fist this?
>
>
> thanks in advance.
>
> Jason
>