This is an automated email from the ASF dual-hosted git repository.
bridgetb pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/drill.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 3d1f705 doc updates
3d1f705 is described below
commit 3d1f705d9b15fc2a7631fdc25c74b68eb2d1a035
Author: Bridget Bevens <[email protected]>
AuthorDate: Thu Jan 24 16:53:35 2019 -0800
doc updates
---
...121-configuring-cgroups-to-control-cpu-usage.md | 4 +--
.../010-compiling-drill-from-source.md | 38 +++++++++++++++-------
2 files changed, 29 insertions(+), 13 deletions(-)
diff --git
a/_docs/configure-drill/121-configuring-cgroups-to-control-cpu-usage.md
b/_docs/configure-drill/121-configuring-cgroups-to-control-cpu-usage.md
index 0cec78d..7b3e9c5 100644
--- a/_docs/configure-drill/121-configuring-cgroups-to-control-cpu-usage.md
+++ b/_docs/configure-drill/121-configuring-cgroups-to-control-cpu-usage.md
@@ -1,6 +1,6 @@
---
title: "Configuring cgroups to Control CPU Usage"
-date: 2019-01-18
+date: 2019-01-25
parent: "Configure Drill"
---
@@ -8,7 +8,7 @@ Starting in Drill 1.13, you can configure a Linux cgroup to
enforce CPU limits o
In Drill 1.13, you had to update the `cgroup.procs` file with the Drill
process ID (PID) each time a Drillbit restarted in order to enforce the CPU
limit for the Drillbit service. As of Drill 1.14, Drill can directly manage
the CPU resources through the Drill start-up script, `drill-env.sh`. You no
longer have to manually add the PID to the `cgroup.procs` file each time a
Drillbit restarts. This step occurs automatically upon restart. The start-up
script checks for the specified cgroup, [...]
-Note: Cgroups V2 is recommended.
+**Note:** cgroups V2 is recommended.
The `drill-env.sh` script contains variables that you must enable for Drill to
directly manage the CPU resources. Uncomment the following variables in
drill-env.sh to enable the feature:
diff --git
a/_docs/developer-information/develop-drill/010-compiling-drill-from-source.md
b/_docs/developer-information/develop-drill/010-compiling-drill-from-source.md
index c495daa..053b248 100644
---
a/_docs/developer-information/develop-drill/010-compiling-drill-from-source.md
+++
b/_docs/developer-information/develop-drill/010-compiling-drill-from-source.md
@@ -1,6 +1,6 @@
---
title: "Compiling Drill from Source"
-date: 2018-12-20
+date: 2019-01-25
parent: "Develop Drill"
---
To develop Drill, you compile Drill from source code and then set up a project
@@ -8,28 +8,44 @@ in Eclipse for use as your development environment. To review
or contribute to
Drill code, you must complete the steps required to install and use the Drill
patch review tool.
+Starting in Drill 1.15, you can build and deploy Apache Drill on the MapR
platform.
+
## Prerequisites
+Apache Drill requires:
+
+- Apache Maven 3.3.1 or later
+- Oracle or OpenJDK 8
- * Apache Maven 3.3.1 or later
- * Oracle or OpenJDK 8
+Apache Drill on the MapR platform also requires:
+
+- MapR 6.x
+- RedHat/CentOS 7.x
-Run the following commands to verify that you have the correct versions of
-Maven and JDK installed:
+Run the following commands to verify that the correct versions of Maven and
JDK are installed:
java -version
- mvn -version
+ mvn -version
+
## 1\. Clone the Repository
git clone https://gitbox.apache.org/repos/asf/drill.git
-## 2\. Compile the Code
+## 2\. Compile the Code
+
+Change to the drill directory:
+
+ cd drill
+
+Build Apache Drill:
+
+ mvn clean install -DskipTests
- cd drill
- mvn clean install -DskipTests
+If you want to deploy Apache Drill on the MapR platform, include the `-Pmapr`
option to build Drill under the MapR profile:
+
+ mvn clean install -DskipTests -Pmapr
-The tarball appears in distribution/target. Move the tarball to a directory
for unpacking, unpack, and then you can connect to Drill and query sample
-data or you can connect Drill to your data sources.
+A tarball is built and appears in the distribution/target directory. Move the
tarball to another directory for unpacking. Unpack the tarball and then connect
to Drill and query sample data, or connect Drill to your data sources.
* To connect Drill to your data sources, refer to [Connect to Data
Sources]({{ site.baseurl }}/docs/connect-a-data-source-introduction) for
instructions.
* To connect to Drill and query sample data, refer to the following topics:
