You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "guoquan (JIRA)" <ji...@apache.org> on 2015/03/18 06:22:47 UTC

[jira] [Updated] (SENTRY-430) Sentry Service does not use correct classpath when HIVE_HOME environment var is defined

     [ https://issues.apache.org/jira/browse/SENTRY-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

guoquan updated SENTRY-430:
---------------------------
    Fix Version/s: 1.5.0

> Sentry Service does not use correct classpath when HIVE_HOME environment var is defined
> ---------------------------------------------------------------------------------------
>
>                 Key: SENTRY-430
>                 URL: https://issues.apache.org/jira/browse/SENTRY-430
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Lenni Kuff
>            Assignee: Prasad Mujumdar
>             Fix For: 1.5.0
>
>         Attachments: SENTRY-430.1.patch, SENTRY-430.2.patch, SENTRY-430.3.patch
>
>
> When HIVE_HOME is set as an environment variable, the Sentry Service will not run with the correct classpath when invoked using "bin/sentry". 
> The code below is from "bin/sentry". Note how if HIVE_HOME is defined nothing from lib/server/* is added to the classpath.
> As a side note, it seems strange that there even is a reference to Hive in this context. It seems that the sentry service is being executed via Hive when HIVE_HOME is defined. It seems like we should not do this.
> {code}
> if [[ -z "$HIVE_HOME" ]]
> then
>   for f in ${SENTRY_HOME}/lib/server/*.jar; do
>     HADOOP_CLASSPATH=${HADOOP_CLASSPATH}:${f}
>   done
>   exec $HADOOP jar ${SENTRY_HOME}/lib/${_CMD_JAR} org.apache.sentry.SentryMain ${args[@]}
> else
>   _HIVE_CMD=${HIVE_HOME}/bin/hive
>   ${_HIVE_CMD} --service jar ${SENTRY_HOME}/lib/${_CMD_JAR} org.apache.sentry.SentryMain ${args[@]}
> fi
> {code}



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