Github user 1ambda commented on the issue:

    https://github.com/apache/zeppelin/pull/1339
  
    Short summary and small thought about #1399 
    
    1. Using symlink like `local-spark/master` would be safe i think. It 
enables user replace his local spark without renaming directories. Currently we 
are using hard coded name.
    
    ```
    SPARK_CACHE="local-spark"
    SPARK_ARCHIVE="spark-${SPARK_VERSION}-bin-hadoop${HADOOP_VERSION}"
    ```
    
    2. about UX, 
    
    - most (experienced in zeppelin) users do not use local spark
    - for new comers, we can provide embedded spark using docker will be 
shipped by #1538 
    - and storking `get-spark` is not too hard even if new users do not use the 
docker images.
    
    3. Now users need to type `get-spark`. it works as described 
    
    ```
    $  zeppelin-review git:(pr/1339) ./bin/zeppelin-daemon.sh start
    Log dir doesn't exist, create 
/Users/1ambda/github/apache-zeppelin/zeppelin-review/logs
    Pid dir doesn't exist, create 
/Users/1ambda/github/apache-zeppelin/zeppelin-review/run
    
    You do not have neither local-spark, nor external SPARK_HOME set up.
    If you want to use Spark interpreter, you need to run get-spark at least 
one time or set SPARK_HOME.
    
    Zeppelin start                                             [  OK  ]
    $  zeppelin-review git:(pr/1339) ./bin/zeppelin-daemon.sh stop
    Zeppelin stop                                              [  OK  ]
    $  zeppelin-review git:(pr/1339) ./bin/zeppelin-daemon.sh get-spark
    Download spark-2.0.1-bin-hadoop2.7.tgz from mirror ...
    
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  
Current
                                     Dload  Upload   Total   Spent    Left  
Speed
    100  178M  100  178M    0     0  7157k      0  0:00:25  0:00:25 --:--:-- 
6953k
    
    spark-2.0.1-bin-hadoop2.7 is successfully downloaded and saved under 
/Users/lambda/github/apache-zeppelin/zeppelin-review/local-spark
    
    $  zeppelin-review git:(pr/1339) ./bin/zeppelin-daemon.sh start
    Zeppelin start                                             [  OK  ]
    ```
    
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to