GitHub user paul-rogers opened a pull request:
https://github.com/apache/drill/pull/547
Drill-4581: Extensive revisions to the Drill launch scripts.
See DRILL-4581 and DRILL-4591 for an overview.
See DRILL-4581 for a detailed list of bugs fixed.
See DRILL-4591 for the motivation for the new "site" directory support.
Changes support DRILL-1170 (Drill-on-YARN).
Broad overview of changes:
* Extended the existing "config" directory concept to create a
"site" directory that holds all site-specific files, leaving the
Drill directory ($DRILL_HOME) to contain only Drill-provided files.
The site directory is handy for all Drill users because it eases
upgrades, but is necessary to simplify Drill-on-YARN deployments.
Use the --config (for backward compatibility) or --site (more
descriptive) option to point to the site directory.
* Moved distribution-specific settings, and Drill defaults, out of
drill-env.sh. Now, drill-env.sh contains only user settings, avoiding
the need to do multi-way merges on upgrades. Distribution-specific
files now reside in a new $DRILL_HOME/conf/distrib-env.sh file.
* Refactored the launch scripts to allow the bulk of setup to be shared
between the "classic" Drill deamon script (drillbit.sh) and the new
Drill-on-YARN scripts.
* Added a new "run" option to drillbit.sh to allow Drill to run as a
child process as needed by tools such as Mesos.
* Changes ensure backward compatibility. Users of earlier releases can
upgrade to the release with this fix without doing anything special.
Drill will "just work." However, users can optionally clean up the
drill-env.sh script, optionally use the site directory, and so on.
Hoever these upgrades are not required.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/paul-rogers/drill DRILL-4581-PR3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/547.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #547
----
commit d9e0e4561d21a3dac3d582254a6b1c9885a6e196
Author: Paul Rogers <prog...@maprtech.com>
Date: 2016-07-12T23:19:28Z
Drill-4581: Extensive revisions to the Drill launch scripts.
See DRILL-4581 and DRILL-4591 for an overview.
See DRILL-4581 for a detailed list of bugs fixed.
See DRILL-4591 for the motivation for the new "site" directory support.
Changes support DRILL-1170 (Drill-on-YARN).
Broad overview of changes:
* Extended the existing "config" directory concept to create a
"site" directory that holds all site-specific files, leaving the
Drill directory ($DRILL_HOME) to contain only Drill-provided files.
The site directory is handy for all Drill users because it eases
upgrades, but is necessary to simplify Drill-on-YARN deployments.
Use the --config (for backward compatibility) or --site (more
descriptive) option to point to the site directory.
* Moved distribution-specific settings, and Drill defaults, out of
drill-env.sh. Now, drill-env.sh contains only user settings, avoiding
the need to do multi-way merges on upgrades. Distribution-specific
files now reside in a new $DRILL_HOME/conf/distrib-env.sh file.
* Refactored the launch scripts to allow the bulk of setup to be shared
between the "classic" Drill deamon script (drillbit.sh) and the new
Drill-on-YARN scripts.
* Added a new "run" option to drillbit.sh to allow Drill to run as a
child process as needed by tools such as Mesos.
* Changes ensure backward compatibility. Users of earlier releases can
upgrade to the release with this fix without doing anything special.
Drill will "just work." However, users can optionally clean up the
drill-env.sh script, optionally use the site directory, and so on.
Hoever these upgrades are not required.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
