You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Quincy HSIEH (JIRA)" <ji...@apache.org> on 2017/07/25 13:19:00 UTC

[jira] [Commented] (SPARK-9776) Another instance of Derby may have already booted the database

    [ https://issues.apache.org/jira/browse/SPARK-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100019#comment-16100019 ] 

Quincy HSIEH commented on SPARK-9776:
-------------------------------------

Hi,

I have this problem when I try to run SparkR shell and PySpark shell at the same time. I don't understand why it tries to initialize the database twice? Can we have singleton factory design pattern to order to ensure that the once the database is initialized, it will always get the same instance? Since I am just a newbie to Spark, what is the difficulty to have such code to avoid to initialize database twice ?

Thank you



> Another instance of Derby may have already booted the database 
> ---------------------------------------------------------------
>
>                 Key: SPARK-9776
>                 URL: https://issues.apache.org/jira/browse/SPARK-9776
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.5.0
>         Environment: Mac Yosemite, spark-1.5.0
>            Reporter: Sudhakar Thota
>         Attachments: SPARK-9776-FL1.rtf
>
>
> val hiveContext = new org.apache.spark.sql.hive.HiveContext(sc) results in error. Though the same works for spark-1.4.1.
> Caused by: ERROR XSDB6: Another instance of Derby may have already booted the database 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org