[jira] [Created] (ZEPPELIN-1660) Home directory references (i.e. ~/zeppelin/) in zeppelin-env.sh don't work as expected

["Ruslan Dautkhanov (JIRA)" <ji...@apache.org>]

Ruslan Dautkhanov created ZEPPELIN-1660:
-------------------------------------------

             Summary: Home directory references (i.e. ~/zeppelin/) in zeppelin-env.sh don't work as expected
                 Key: ZEPPELIN-1660
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1660
             Project: Zeppelin
          Issue Type: Bug
          Components: conf, zeppelin-server
    Affects Versions: 0.6.2
         Environment: Java 7
RHEL 6
            Reporter: Ruslan Dautkhanov


We want to have template for Zeppelin conf files and a skelton of user-owned directories for each Zeppelin instance, so have to have configuration file zeppelin-env.sh to not have absolute paths, but relative to each user's home directory. "~" unix-type directory references don't work in Zeppelin.

Have following settings in zeppelin-env.sh that reference current user's home directory subdirectories under "zeppelin":
{noformat}
export ZEPPELIN_LOG_DIR="~/zeppelin/log"
export ZEPPELIN_PID_DIR="~/zeppelin/run"
export ZEPPELIN_WAR_TEMPDIR="~/zeppelin/tmp"
export ZEPPELIN_NOTEBOOK_DIR="~/zeppelin/notebooks"
{noformat}

Attempt to start zeppelin.sh --config ~/zeppelin/conf/ 
shows
{noformat}
Log dir doesn't exist, create ~/zeppelin/log
Pid dir doesn't exist, create ~/zeppelin/run
Pid dir doesn't exist, create ~/zeppelin/notebooks
{noformat}

Zeppelin actually creates a directory names "~"/zeppelin (yes, with tilde character, with underneath directory named "zeppelin") in the current directory.

We want to have template for Zeppelin conf files and a skelton of user-owned directories for each Zeppelin instance, so have to have configuration file zeppelin-env.sh to not have absolute paths, but relative to each user's home directory. "~" unix-type directory references don't work in Zeppelin.

ps. We also tried to use "~user/zeppelin" - for the sake of completeness of the tests -- the same issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)