[
https://issues.apache.org/jira/browse/DRILL-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405155#comment-15405155
]
ASF GitHub Bot commented on DRILL-4822:
---------------------------------------
Github user paul-rogers commented on the issue:
https://github.com/apache/drill/pull/558
$DRILL_SITE means the site directory. At present, I don't believe we have a
$DRILL_ENV/env directory. The site directory is meant to be a location, outside
of $DRILL_HOME, that contains site-specific files such as configuration, jars
and native libraries.
The scripts handle the "classic" case: the files are in $DRILL_HOME (in
conf, jars/3rdparty, etc.) The scripts should also handle the obscure classic
case in which Drill allows config in /etc/drill. The code in question here
applies only to the case when using a site directory that is not one of the
classic locations.
> Extend distrib-env.sh search to consider site directory
> -------------------------------------------------------
>
> Key: DRILL-4822
> URL: https://issues.apache.org/jira/browse/DRILL-4822
> Project: Apache Drill
> Issue Type: Improvement
> Reporter: Paul Rogers
> Priority: Minor
>
> DRILL-4581 provided revisions to the Drill launch scripts. As part of that
> fix, we introduced a new distrib-env.sh file to hold settings created by
> custom Drill installers (that is, by custom distributions.) The original
> version of this feature looks for distrib-env.sh only in $DRILL_HOME/env.
> Experience suggests that installers will write site-specific values to
> distrib-env.sh and so the file must then be copied to $DRILL_SITE when
> running under YARN. Add $DRILL_SITE to the search path in drill-config.sh for
> distrib-env.sh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
