Re: Another instance of Derby already booted the database .../metastore_db

2017-01-27 Thread Felix Cheung
Brenner mailto:pbren...@placeiq.com>> Sent: Friday, January 27, 2017 8:01 AM Subject: Another instance of Derby already booted the database .../metastore_db To: mailto:users@zeppelin.apache.org>> We had this same problem. Copying or symlinking hive-site.xml to the zeppelin conf direct

Another instance of Derby already booted the database .../metastore_db

2017-01-27 Thread Paul Brenner
We had this same problem. Copying or symlinking hive-site.xml to the zeppelin conf directory and then restarting solved it for us.  http://www.placeiq.com/ http://www.placeiq.com/ http://www.placeiq.com/ Paul Brenner https://twitter.com/placeiq https://twitter.com/placeiq https://twitter.com/p

Another instance of Derby already booted the database .../metastore_db

2017-01-27 Thread Jan Rasehorn
Hello, I was running into an issue with a query on a temp table and to test it I opened another notebook in another tab. When I execute this new notebook, I got an error: Caused by: java.sql.SQLException: Failed to start database 'metastore_db' with class loader org.apache.spark.sql.hive.client.I