You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Paul Rogers (JIRA)" <ji...@apache.org> on 2017/10/04 04:55:02 UTC
[jira] [Created] (DRILL-5835) Deprecate special, hard-coded
directories in Drill launch scripts
Paul Rogers created DRILL-5835:
----------------------------------
Summary: Deprecate special, hard-coded directories in Drill launch scripts
Key: DRILL-5835
URL: https://issues.apache.org/jira/browse/DRILL-5835
Project: Apache Drill
Issue Type: Improvement
Affects Versions: 1.10.0
Reporter: Paul Rogers
Priority: Minor
Drill, since version 1.0, has attached special meaning to two global directories:
* {{/var/drill/log}} -- Default location for logs
* {{/etc/drill/conf}} -- Default location for config files
These locations are used by Drill QA to preserve files across Drill installs. All good.
However, as we automate testing, as we run multiple Drillbits per node, and as we host under YARN, these directories are becoming more of a problem than a help.
Proposed is:
* Deprecate these two directories
* Instruct QA (and other users) to use the {{--site}} option when launching Drill to point to the Drill "site" directory that can contain these files.
The site directory can be {{/etc/drill/conf}} or any other location. The {{drill-env.sh}} in that directory can point {{DRILL_LOG_DIR}} to {{/var/log/drill}}. But, by default, two different Drill installations won't try to overwrite each other's files as is done today.
QA still gets what they want (files that stay constant across Drill installs), but we end up with many fewer test cases for the launch scripts because we don't have to (awkwardly) test the shared, global directories.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)