[
https://issues.apache.org/jira/browse/SENTRY-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139202#comment-14139202
]
Prasad Mujumdar commented on SENTRY-430:
----------------------------------------
One of the things config tool supports is the mock verification of the query.
For that it invokes hive locally (or can connect to HS2) to compile the query
and pass it through Sentry validation. Thus it will need hive configuration.
However, we certainly can separate that out from rest of the Sentry script.
That way we can avoid depending on Hive properties for setting our classpath.
will get a patch out shortly. Thanks!
> 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: Arun Suresh
>
> 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)
