[
https://issues.apache.org/jira/browse/DRILL-5042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15672821#comment-15672821
]
Paul Rogers commented on DRILL-5042:
------------------------------------
Prior to 1.8 we had just one file: drill-env.sh. It contained the user's
settings, Drill's defaults and distribution-specific settings. The drawback was
that, on each new install of a distro, the user had to do a three-way merge:
identify what Drill changed, what the distro changed and merge them with what
the user changed.
With the split files, Drill defaults are in drill-config.sh, distro-specific
settings are in distrib-env.sh and the user's settings are in drill-env.sh. No
merging on new installs.
Plus, if the user also employs a site directory, all user-specific files
(including in drill-env.sh) reside in a separate directory. To install a new
Drill distro, just delete the old one and install the new one. No merging, no
copying, no nothin'.
> Settings in drill-env.sh are not overriding the same settings in
> distrib-env.sh
> -------------------------------------------------------------------------------
>
> Key: DRILL-5042
> URL: https://issues.apache.org/jira/browse/DRILL-5042
> Project: Apache Drill
> Issue Type: Bug
> Components: Tools, Build & Test
> Affects Versions: 1.9.0
> Reporter: Krystal
> Assignee: Paul Rogers
>
> commit id: d925f738d006caedf8635db1024825e355b5dada
> currently, settings from drill-env.sh are not overriding those from
> distrib-env.sh. Instead, the ones from distrib-env.sh are overriding the
> same setting from drill-env.sh.
> The correct behavior is that the settings from drill-env.sh should override
> the same settings in distrib-env.sh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
