hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mich Talebzadeh" <>
Subject starting spark-shell throws /tmp/hive on HDFS should be writable error
Date Fri, 20 Nov 2015 21:13:58 GMT


Has this been resolved. I don't think this has anything to do with /tmp/hive
directory permission



log4j:WARN No appenders could be found for logger

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See for
more info.

Using Spark's repl log4j profile:

To adjust logging level use sc.setLogLevel("INFO")

Welcome to

      ____              __

     / __/__  ___ _____/ /__

    _\ \/ _ \/ _ `/ __/  '_/

   /___/ .__/\_,_/_/ /_/\_\   version 1.5.2



Using Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java

Type in expressions to have them evaluated.

Type :help for more information.

java.lang.RuntimeException: java.lang.RuntimeException: The root scratch
dir: /tmp/hive on HDFS should be writable. Current permissions are:



<console>:10: error: not found: value sqlContext

       import sqlContext.implicits._


<console>:10: error: not found: value sqlContext

       import sqlContext.sql








Mich Talebzadeh


Sybase ASE 15 Gold Medal Award 2008

A Winning Strategy: Running the most Critical Financial Data on ASE 15


Author of the books "A Practitioner's Guide to Upgrading to Sybase ASE 15",
ISBN 978-0-9563693-0-7. 

co-author "Sybase Transact SQL Guidelines Best Practices", ISBN

Publications due shortly:

Complex Event Processing in Heterogeneous Environments, ISBN:

Oracle and Sybase, Concepts and Contrasts, ISBN: 978-0-9563693-1-4, volume
one out shortly




NOTE: The information in this email is proprietary and confidential. This
message is for the designated recipient only, if you are not the intended
recipient, you should destroy it immediately. Any information in this
message shall not be understood as given or endorsed by Peridale Technology
Ltd, its subsidiaries or their employees, unless expressly so stated. It is
the responsibility of the recipient to ensure that this email is virus free,
therefore neither Peridale Ltd, its subsidiaries nor their employees accept
any responsibility.


View raw message