This is an automated email from the ASF dual-hosted git repository.
bridgetb pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/drill-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 09fac27 add web ui features to drill doc for 1.16
09fac27 is described below
commit 09fac276e7c1078ce180b1425725c767a961c4cf
Author: Bridget Bevens <[email protected]>
AuthorDate: Thu Apr 18 12:21:50 2019 -0700
add web ui features to drill doc for 1.16
---
docs/configuring-storage-plugins/index.html | 10 +-
docs/img/ui-export-all.png | Bin 0 -> 39876 bytes
docs/img/ui-limit-results-warn.png | Bin 0 -> 13718 bytes
docs/img/ui-options.PNG | Bin 0 -> 41028 bytes
docs/img/ui-order-duration.png | Bin 0 -> 56440 bytes
docs/img/ui-results-page.png | Bin 0 -> 101904 bytes
docs/img/ui-row-limit.png | Bin 0 -> 34559 bytes
docs/img/ui-spilled-data.png | Bin 0 -> 318 bytes
docs/img/ui-submit-popup.png | Bin 0 -> 25778 bytes
docs/img/ui-turtle-wait.png | Bin 0 -> 677 bytes
docs/img/ui-wait-op.png | Bin 0 -> 369 bytes
docs/planning-and-execution-options/index.html | 60 ++++++++++-
docs/query-data-introduction/index.html | 47 +++++---
docs/query-profiles/index.html | 120 ++++++++++++++++++---
docs/rest-api-introduction/index.html | 7 +-
docs/starting-the-web-ui/index.html | 24 +++--
.../index.html | 4 +-
feed.xml | 4 +-
18 files changed, 225 insertions(+), 51 deletions(-)
diff --git a/docs/configuring-storage-plugins/index.html
b/docs/configuring-storage-plugins/index.html
index d2ea514..02784ac 100644
--- a/docs/configuring-storage-plugins/index.html
+++ b/docs/configuring-storage-plugins/index.html
@@ -1310,7 +1310,7 @@
</div>
- Dec 8, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1405,11 +1405,15 @@ The file is removed after Drill uses the file for the
first time.<br></li>
<h2 id="exporting-storage-plugin-configurations">Exporting Storage Plugin
Configurations</h2>
-<p>Starting in Drill 1.14, you can export and save your storage plugin
configurations from the Storage page in the Drill Web UI. The Export option
next to each enabled storage plugin provides an easy way to export your storage
plugin configurations to a JSON file when you want to save and reuse the
configurations. For example, before an upgrade. </p>
+<p>Starting in Drill 1.14, you can export and save your storage plugin
configurations from the Storage page in the Drill Web UI. The Export option
next to each enabled storage plugin provides an easy way to export each storage
plugin configuration to a JSON file when you want to save and reuse the
configurations. For example, before an upgrade. </p>
<p><img src="https://i.imgur.com/MnLY75q.png"; alt=""> </p>
-<p>You can also access the Export option on the Update page, by selecting the
Update option next to an enabled or disabled storage plugin. </p>
+<p>You can also access the Export option on the Update page, by selecting the
Update option next to an enabled or disabled storage plugin. </p>
+
+<p>Starting in Drill 1.16, you can export all storage plugin configurations at
once, by clicking the Export All button. You have the option to export all
storage plugin configurations to a HOCON format (.conf file) or a JSON file.
</p>
+
+<p><img src="https://i.imgur.com/91ubjpb.png"; alt=""></p>
<p>When you need to configure the storage plugin, copy and paste the contents
of the JSON file into the Configuration field. You can access the Configuration
field for a storage plugin by selecting Update next to the storage plugin.</p>
diff --git a/docs/img/ui-export-all.png b/docs/img/ui-export-all.png
new file mode 100644
index 0000000..cfb932c
Binary files /dev/null and b/docs/img/ui-export-all.png differ
diff --git a/docs/img/ui-limit-results-warn.png
b/docs/img/ui-limit-results-warn.png
new file mode 100644
index 0000000..1a10b7a
Binary files /dev/null and b/docs/img/ui-limit-results-warn.png differ
diff --git a/docs/img/ui-options.PNG b/docs/img/ui-options.PNG
new file mode 100644
index 0000000..aea171e
Binary files /dev/null and b/docs/img/ui-options.PNG differ
diff --git a/docs/img/ui-order-duration.png b/docs/img/ui-order-duration.png
new file mode 100644
index 0000000..acfc146
Binary files /dev/null and b/docs/img/ui-order-duration.png differ
diff --git a/docs/img/ui-results-page.png b/docs/img/ui-results-page.png
new file mode 100644
index 0000000..ff7cc18
Binary files /dev/null and b/docs/img/ui-results-page.png differ
diff --git a/docs/img/ui-row-limit.png b/docs/img/ui-row-limit.png
new file mode 100644
index 0000000..063c93b
Binary files /dev/null and b/docs/img/ui-row-limit.png differ
diff --git a/docs/img/ui-spilled-data.png b/docs/img/ui-spilled-data.png
new file mode 100644
index 0000000..4e5a75d
Binary files /dev/null and b/docs/img/ui-spilled-data.png differ
diff --git a/docs/img/ui-submit-popup.png b/docs/img/ui-submit-popup.png
new file mode 100644
index 0000000..50bb865
Binary files /dev/null and b/docs/img/ui-submit-popup.png differ
diff --git a/docs/img/ui-turtle-wait.png b/docs/img/ui-turtle-wait.png
new file mode 100644
index 0000000..f83f60d
Binary files /dev/null and b/docs/img/ui-turtle-wait.png differ
diff --git a/docs/img/ui-wait-op.png b/docs/img/ui-wait-op.png
new file mode 100644
index 0000000..49b813c
Binary files /dev/null and b/docs/img/ui-wait-op.png differ
diff --git a/docs/planning-and-execution-options/index.html
b/docs/planning-and-execution-options/index.html
index 77cf33b..bb0b479 100644
--- a/docs/planning-and-execution-options/index.html
+++ b/docs/planning-and-execution-options/index.html
@@ -1310,7 +1310,7 @@
</div>
- Dec 28, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1349,14 +1349,14 @@ persist across all sessions. </p>
<h3 id="setting-options-from-the-drill-web-ui">Setting Options from the Drill
Web UI</h3>
-<p>When Drill is running, you can access the Drill Web UI at
<code>http://<drill-hostname>:8047/</code>. The Drill Web UI has an
Options button located in the upper right corner that you can click to display
an Options page. The Options page lists all the Drill options that you can set.
When you set options from this page, you are setting the options at the system
level. To override an option for the duration of a session, set the option from
the Drill shell using the SET command. </p>
+<p>When Drill is running, you can access the Drill Web UI at
<code>http://<drill-hostname>:8047/</code>. The Drill Web UI has an
Options button located in the upper right corner that you can click to display
an Options page. The Options page lists all the Drill options that you can set.
When you set options from this page, you are setting the options at the system
level. To override an option for the duration of a session, set the option from
the Drill shell using the SET command. </p>
-<p><img src="https://i.imgur.com/SQH3YNT.png"; alt=""> </p>
+<p><img src="https://i.imgur.com/WMij8gQ.png"; alt=""> </p>
<p>Starting in Drill 1.15, the Options page includes the following
enhancements: </p>
<p><strong>Search Field</strong><br>
-The search field enables you to quickly search across all available Drill
configuration options to quickly find options you are interested in. For
example, you can search on the keyword "memory" for a list of all
options related to configuring Drill memory.</p>
+The search field enables you to quickly search across all available Drill
configuration options to quickly find options you are interested in. For
example, you can search on the keyword "memory" for a list of all
options related to configuring Drill memory. Starting in Drill 1.16, the Search
field contains an x that clears the search field when clicked. </p>
<p><strong>Quick Filters</strong><br>
Next to the search field are quick filter buttons that filter options by
important keywords in one click. For example, the "planner" quick
filter button quickly lists all options related to the query planner. The query
planning options are prepended by the keyword "planner." Quick
filters return options that include the keyword in the option name and/or
description. </p>
@@ -1396,7 +1396,57 @@ Issuing <code>select timestamp '2008-2-23
12:23:34' from (values(1))</co
<div class="highlight"><pre><code class="language-text"
data-lang="text">2008-02-23T12:23:34
</code></pre></div>
<p>Issuing the query after setting the
<code>web.display_format.timestamp</code> option to the format <code>yyyy-MM-dd
HH:mm:ss.SS</code> returns the following results in the Web UI: </p>
-<div class="highlight"><pre><code class="language-text"
data-lang="text">2008-02-23 12:23:34.00
+<div class="highlight"><pre><code class="language-text"
data-lang="text">2008-02-23 12:23:34.00
+</code></pre></div>
+<h2 id="limiting-the-number-of-rows-returned-for-result-sets">Limiting the
Number of Rows Returned for Result Sets</h2>
+
+<p>The <code>exec.query.max_rows</code> option, introduced in Drill 1.16,
automatically limits the number of rows that Drill returns from a result set.
When you configure a limit, the limit is automatically applied by Drill when
you run a query. You do not need to include the LIMIT clause. Configuring a
limit on results reduces the amount of processing and streaming work for the
web server when using the Drill WEb UI. </p>
+
+<p>The default setting for <code>exec.query.max_rows</code> is 0, which
indicates no limit; queries will return all results. An administrator can
modify the exec.query.max_rows setting at the system level (setting persists
across restarts) from the Options page in the Drill Web UI or using the ALTER
SYSTEM command. Alternatively, the option can be set at the session level
(valid for a user session only) using the SET command or from SQLLine. </p>
+
+<p><strong>Session Level</strong><br>
+To set the <code>exec.query.max_rows</code> option per user session, use the
SET command or the SQLLine line command, as shown: </p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">SET
`exec.query.max_rows` = <value>;
+!set rowlimit <value>
+</code></pre></div>
+<p><strong>System Level</strong><br>
+To set the <code>exec.query.max_rows</code> option such that it persists
across users, change the setting in the Drill Web UI
(<code>http://<drill-hostname>:8047/options</code>) or use the ALTER
SYSTEM SET command, as shown: </p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">ALTER
SYSTEM SET `exec.query.max_rows` = <value>;
+</code></pre></div>
+<hr>
+
+<p><strong>NOTE</strong><br>
+The <code>exec.query.max_rows</code> option overrides row limit settings
configured in the Drill Web UI and <code>drill-override.conf</code> file, which
are described below. </p>
+
+<hr>
+
+<h3 id="drill-web-ui-row-limit-settings">Drill Web UI Row Limit Settings</h3>
+
+<p>In addition to the <code>exec.query.max_rows</code> option, the Query page
in the Drill Web UI provides a field where you can enter a limit on the number
of rows returned from a result set when you run a query. </p>
+
+<p><strong>Note:</strong> You can also configure the row limit for a REST
client through the <a
href="/docs/rest-api-introduction/#post-query-json">autoLimit parameter in the
REST API</a>. </p>
+
+<p><img src="https://i.imgur.com/7nF0RBq.png"; alt=""><br>
+When you submit the query, results display across one or multiple pages. You
can set the number of results that display per page. When results span multiple
pages, scroll through the pages using the links in the bottom right corner of
the screen.
+<img src="https://i.imgur.com/eYn22NL.png"; alt=""><br>
+Clicking the Query Profile tab at the top of the results page displays the
query profile with a warning stating that the results were automatically
limited.
+<img src="https://i.imgur.com/L4Yx666.png"; alt=""><br>
+Note that the <code>exec.query.max_rows</code> setting overrides the setting
in the Web UI. For example, if the <code>exec.query.max_rows</code> option is
set to 10 and you limit results to 20 on the Query page in the Web UI, Drill
only returns 10 rows from the result set. </p>
+
+<h3 id="drill-override-conf-row-limit-settings">Drill-override.conf Row Limit
Settings</h3>
+
+<p>The <code>drill-override.conf</code> file contains the same row limit
setting as the Drill Web UI; however, the setting in the
<code>drill-override.conf</code> file overrides the limit set in the Drill Web
UI. Note that the <code>exec.query.max_rows</code> option overrides the setting
in <code>drill-override.conf</code> and the Drill Web UI. You must restart the
Drillbit after you modify <code>drill-override.conf</code>. </p>
+
+<p>Add the following configuration to <code>drill-override.conf</code>,
changing the row limit setting and rows per page setting, as needed: </p>
+<div class="highlight"><pre><code class="language-text"
data-lang="text">drill.exec.http: {
+ web.client.resultset: {
+ autolimit {
+ enable: true,
+ rows: 1000
+ },
+ defaultRowsPerPage: 10
+ }
+}
</code></pre></div>
diff --git a/docs/query-data-introduction/index.html
b/docs/query-data-introduction/index.html
index 4b10870..6c4db60 100644
--- a/docs/query-data-introduction/index.html
+++ b/docs/query-data-introduction/index.html
@@ -1308,22 +1308,48 @@
</div>
- Dec 8, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
<div class="int_text" align="left">
- <p>You can query local and distributed file systems, Hive, HBase data,
complex data, INFORMATION SCHEMA, and system tables as described in the
subtopics of this section. </p>
+ <p>You can submit SQL queries against various data sources from the <a
href="/docs/configuring-the-drill-shell/">Drill shell (SQLLine)</a>, <a
href="/docs/starting-the-web-ui/">Drill Web UI</a>, <a
href="/docs/rest-api/">REST API</a>, and tools that connect to Drill via <a
href="/docs/odbc-jdbc-interfaces/">ODBC or JDBC</a>. Drill has <a
href="/docs/connect-a-data-source-introduction/">several storage and format
plugins</a> that enable queries against multiple data sources and da [...]
-<p>The query specifies the data source location and includes data casting. </p>
+<p>The following sections provide some general information about Drill
queries.</p>
<h2 id="specifying-the-data-source-location">Specifying the Data Source
Location</h2>
-<p>The optional <a href="/docs/use">USE statement</a> runs subsequent queries
against a particular <a
href="/docs/connect-a-data-source-introduction/">storage plugin</a>. The USE
statement typically saves typing some of the storage plugin information in the
FROM statement. If you omit the USE statement, specify a storage plugin, such
as dfs, and optionally a workspace, such as default, and a path to the data
source using dot notation and back ticks. For example:</p>
-
-<p><code>dfs.`default`.`/Users/drill-user/apache-drill-1.1.0/log/sqlline_queries.json</code>`;</p>
+<p>The optional <a href="/docs/use">USE command</a> runs subsequent queries
against a particular <a
href="/docs/connect-a-data-source-introduction/">storage plugin or schema</a>.
When you run the USE command to switch to a particular storage plugin or
schema, you do not have to include the full path to the data in the FROM
clause, for example:</p>
+<p>The following query was run before switching to the dfs.schema. A workspace
named "samples" was configured in the dfs storage plugin, creating a
schema named <code>dfs.samples</code>. Notice that you have to use dot notation
for the schema and back ticks around the table name. In some cases you may
point to a directory or file in the schema, in which case you would put back
ticks around the entire path, for example
<code>dfs.samples.`/nation/data/nation.parquet/</code>`. </p>
+<div class="highlight"><pre><code class="language-text"
data-lang="text">apache drill> select * from dfs.samples.`nation1`;
++-------------+----------------+-------------+----------------------+
+| N_NATIONKEY | N_NAME | N_REGIONKEY | N_COMMENT |
++-------------+----------------+-------------+----------------------+
+| 0 | ALGERIA | 0 | haggle. carefully f |
+| 1 | ARGENTINA | 1 | al foxes promise sly |
+...
++-------------+----------------+-------------+----------------------+
+</code></pre></div>
+<p>Running USE to switch to the <code>dfs.samples</code> schema: </p>
+<div class="highlight"><pre><code class="language-text"
data-lang="text">apache drill> use dfs.samples;
++------+-----------------------------------------+
+| ok | summary |
++------+-----------------------------------------+
+| true | Default schema changed to [dfs.samples] |
++------+-----------------------------------------+
+</code></pre></div>
+<p>Query written without identifying the schema (without dot notation or back
ticks):</p>
+<div class="highlight"><pre><code class="language-text"
data-lang="text">apache drill (dfs.samples)> select * from nation1;
++-------------+----------------+-------------+----------------------+
+| N_NATIONKEY | N_NAME | N_REGIONKEY | N_COMMENT |
++-------------+----------------+-------------+----------------------+
+| 0 | ALGERIA | 0 | haggle. carefully f |
+| 1 | ARGENTINA | 1 | al foxes promise sly |
+...
++-------------+----------------+-------------+----------------------+
+</code></pre></div>
<h2 id="casting-data">Casting Data</h2>
<p>In some cases, Drill converts schema-less data to correctly-typed data
implicitly. In this case, you do not need to <a
href="/docs/supported-data-types/#casting-and-converting-data-types">cast the
data</a> to another type. The file format of the data and the nature of your
query determines the requirement for casting or converting. Differences in
casting depend on the data source. </p>
@@ -1335,14 +1361,11 @@ or an aggregate function.</p>
<h2 id="troubleshooting-queries">Troubleshooting Queries</h2>
-<p>In addition to testing queries interactively in the Drill shell, and
examining error messages, use the <a href="/docs/explain/">EXPLAIN command</a>
to analyze errors and troubleshoot queries
-that do not run. For example, if you run into a casting error, the query plan
-text may help you isolate the problem.</p>
+<p>In addition to analyzing error messages printed by the Drill shell, you can
troubleshoot queries from the <a
href="/docs/identifying-performance-issues/">Profiles page</a> in the Drill Web
UI or run the <a href="/docs/explain/">EXPLAIN command</a> to review the query
plan for issues. For example, if you run into a casting error, the query plan
text may help you isolate the problem.</p>
<div class="highlight"><pre><code class="language-text" data-lang="text">0:
jdbc:drill:zk=local> !set maxwidth 10000
-0: jdbc:drill:zk=local> explain plan for select ... ;
+0: jdbc:drill:zk=local> explain plan for <query>;
</code></pre></div>
-<p><a href="/docs/configuring-the-drill-shell/">Drill shell commands</a>
include the <code>!set <set variable> <value></code> to increase
the default text display (number of characters). By
-default, most of the plan output is hidden.</p>
+<p><a href="/docs/configuring-the-drill-shell/">Drill shell commands</a>
include the <code>!set <set variable> <value></code> to increase
the default text display (number of characters). By default, most of the plan
output is hidden.</p>
<h2 id="query-syntax-tips">Query Syntax Tips</h2>
diff --git a/docs/query-profiles/index.html b/docs/query-profiles/index.html
index 7f384bd..ff96271 100644
--- a/docs/query-profiles/index.html
+++ b/docs/query-profiles/index.html
@@ -1310,37 +1310,32 @@
</div>
- Dec 8, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
<div class="int_text" align="left">
- <p>A profile is a summary of metrics collected for each query that
Drill executes. Query profiles provide information that you can use to monitor
and analyze query performance. When Drill executes a query, Drill writes the
profile of each query to disk, which is either the local filesystem or a
distributed file system, such as HDFS. As of Drill 1.11, Drill can <a
href="/docs/start-up-options/#configuring-start-up-options">store profiles in
memory</a> instead of writing them to di [...]
+ <p>A profile is a summary of metrics collected for each query that
Drill executes. Query profiles provide information that you can use to monitor
and analyze query performance. When Drill executes a query, Drill writes the
profile of each query to disk, which is either the local filesystem or a
distributed file system, such as HDFS. As of Drill 1.11, Drill can <a
href="/docs/start-up-options/#configuring-start-up-options">store profiles in
memory</a> instead of writing them to di [...]
-<h2 id="query-profiles-in-the-drill-web-ui">Query Profiles in the Drill Web
UI</h2>
+<p>The Drill Web UI provides aggregate statistics across profile lists.
Profile lists consist of data from major and minor fragments, operators, and
input streams. Use query profiles in conjunction with Drill logs to debug
issues. </p>
-<p>The Drill Web UI provides aggregate statistics across profile lists.
Profile lists consist of data from major and minor fragments, operators, and
input streams. You can use profiles in conjunction with Drill logs for
debugging purposes. In addition to viewing query profiles, you can modify,
resubmit, or cancel queries from the Drill Web UI. </p>
+<h2 id="viewing-a-query-profile">Viewing a Query Profile</h2>
-<h3 id="query-fragment-and-operator-identifiers">Query, Fragment, and Operator
Identifiers</h3>
+<p>You can view query profiles in the Profiles tab of the Drill Web UI. When
you select the Profiles tab, you see a list of queries than ran or are
currently running in the cluster. </p>
-<p>Metrics in a query profile are associated with a coordinate system of
identifiers. Drill uses a coordinate system comprised of query, fragment, and
operator identifiers to track query execution activities and resources. Drill
assigns a unique identifier, the QueryID, to each query received and then
assigns an identifier to each fragment and operator that executes the query. An
example of a QueryID is 2aa98add-15b3-e155-5669-603c03bfde86. The following
images shows an example of fragme [...]
+<p><img src="/docs/img/list_queries.png" alt=""> </p>
-<p><img src="/docs/img/xx-xx-xx.png" alt=""> </p>
-
-<h3 id="viewing-a-query-profile">Viewing a Query Profile</h3>
+<p>Starting in Drill 1.16, you can sort the columns on the Profiles page. For
example, if you want to quickly locate queries with the longest running times,
you can sort the Duration column in descending order such that the longest
running queries appear at the top of the list. You can also use the Search
Profiles field to filter the list of query profiles and then use the sort
feature.</p>
-<p>You can view query profiles in the Profiles tab of the Drill Web UI. When
you select the Profiles tab, you see a list of the last 100 queries than ran or
are currently running in the cluster. </p>
+<p>For example, the following image shows the query profiles filtered by the
mapr user on a specific date with the Duration column sorted in descending
order: </p>
-<p><img src="/docs/img/list_queries.png" alt=""></p>
+<p><img src="https://i.imgur.com/IVA2fKG.png"; alt=""></p>
-<p>You must click on a query to see its profile. </p>
+<p>To see the profile for a specific query, click on the query in the profiles
list. </p>
-<p><img src="/docs/img/query_profile.png" alt=""> </p>
+<p><img src="/docs/img/query_profile.png" alt=""> </p>
-<p>When you select a profile, notice that the URL in the address bar contains
the QueryID, as shown in the following URL:</p>
-<div class="highlight"><pre><code class="language-text" data-lang="text">
http://<drill_node>:8047/profiles/2aa98add-15b3-e155-5669-603c03bfde86
-</code></pre></div>
<p>The Query Profile section summarizes a few key details about the query,
including: </p>
<ul>
@@ -1349,7 +1344,98 @@
<li>The total number of minor fragments required to execute the query.</li>
</ul>
-<p>Further down you can see the Fragment Profiles and Operator Profiles
sections. </p>
+<p>When you select a profile, notice that the URL in the address bar contains
the QueryID, as shown in the following URL:</p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">
http://<drill_node>:8047/profiles/2aa98add-15b3-e155-5669-603c03bfde86
+</code></pre></div>
+<h2 id="query-fragment-and-operator-identifiers">Query, Fragment, and Operator
Identifiers</h2>
+
+<p>Metrics in a query profile are associated with a coordinate system of
identifiers. Drill uses a coordinate system comprised of query, fragment, and
operator identifiers to track query execution activities and resources. Drill
assigns a unique identifier, the QueryID, to each query received and then
assigns an identifier to each fragment and operator that executes the query. An
example of a QueryID is 2aa98add-15b3-e155-5669-603c03bfde86. The following
image shows an example of fragmen [...]
+
+<p><img src="/docs/img/xx-xx-xx.png" alt=""> </p>
+
+<h2 id="query-profile-warnings">Query Profile Warnings</h2>
+
+<p>When Drill executes a query, the workload should be uniformly distributed
across the fragments and operators processing the data. When you evaluate a
query profile in the Drill Web UI, seeing a disproportionate distribution of
work across fragments (in terms of time) or excess memory use typically
indicates performance issues and requires some performance tuning. </p>
+
+<p>Starting in Drill 1.16, the Drill Web UI displays warning messages in the
query profile for the following issues: </p>
+
+<ul>
+<li>No query progress within a certain amount of time<br></li>
+<li>Operators spilling data to disk (operators do not have enough memory to
complete operations completely in-memory)<br></li>
+<li>Operators spending significantly more time waiting for data than
processing it </li>
+</ul>
+
+<p>In addition to the warnings, the Operator Profiles section of the query
profile also displays an icon in the column to indicate which operator is
askew. </p>
+
+<p>The following table lists the warnings, icons, configurable options related
to the warnings, and option descriptions: </p>
+
+<table><thead>
+<tr>
+<th>Warning Message</th>
+<th>Icon</th>
+<th>Related Option(s)</th>
+<th>Description</th>
+</tr>
+</thead><tbody>
+<tr>
+<td>!WARNING: No fragments have made any progress in the last 300 seconds.
(See Last Progress below.)</td>
+<td>None</td>
+<td>drill.exec.http.profile.warning.progress.threshold</td>
+<td>If none of the fragments make any progress within the set time, a
warning displays. Time is set in seconds. Default is 300 seconds (5 minutes).
You can see fragment activity in the Fragment Profiles section of the query
profile.</td>
+</tr>
+<tr>
+<td>!WARNING: Some operators have data spilled to disk. This will result in
performance loss. (See Avg Peak memory and Max Peak Memory below)</td>
+<td><img src="https://i.imgur.com/rnT6Uq5.png"; alt=""> Look for the icon in
the Avg Peak Memory and Max Peak Memory columns to find the operators that
spilled data to disk.</td>
+<td>See <a
href="https://drill.apache.org/docs/sort-based-and-hash-based-memory-constrained-operators/";>Sort-Based
and Hash-Based Memory Constrained Operators</a> for related options.</td>
+<td>Hovering the mouse over the icon reveals the average number of spills. The
higher the value, the greater the degradation.</td>
+</tr>
+<tr>
+<td>!WARNING: Some of the operators spent more time waiting for data than
processing it. (See AVG WAIT TIME as compared to Average Process Time for the
operators below.)</td>
+<td><img src="https://i.imgur.com/hxwsiaA.png"; alt=""> Look for the icon in
the Max Process Time or Max Wait Time columns to locate the operators that
waited or processed too long.</td>
+<td>drill.exec.http.profile.warning.time.skew.min</td>
+<td>Sets the minimum threshold for operators with the longest processing or
waiting fragment. When the slowest fragment hits this threshold and runs or
waits at least 2X (default setting) longer than the average fragment, the
Drill Web UI displays a warning message. Default is 2. The
drill.exec.http.profile.warning.time.skew.ratio.process option sets the
threshold ratio for processing. The
drill.exec.http.profile.warning.time.skew.ratio.wait option sets the thres [...]
+</tr>
+<tr>
+<td>See warning for drill.exec.http.profile.warning.time.skew.min</td>
+<td></td>
+<td>drill.exec.http.profile.warning.time.skew.ratio.process</td>
+<td>Defines the threshold ratio for processing. When the
maxProcessing:avgProcessing ratio exceeds the defined threshold, the Drill Web
UI displays a skew warning. Default is 2.</td>
+</tr>
+<tr>
+<td>See warning for drill.exec.http.profile.warning.time.skew.min</td>
+<td></td>
+<td>drill.exec.http.profile.warning.time.skew.ratio.wait</td>
+<td>Defines the threshold ratio for waiting. When the maxWait:avgWait ratio
exceeds the defined threshold, the Drill Web UI displays a skew warning.
Default is 2.</td>
+</tr>
+<tr>
+<td>!WARNING: Some of the SCAN operators spent more time waiting for data than
processing it. (See AVG WAIT TIME as compared to Average Process Time for the
scan operators below.)</td>
+<td><img src="https://i.imgur.com/HHA5CkV.png"; alt=""> Look for the icon in
the Avg Wait Time or Avg Process Time columns to locate the scan operators that
waited too long.</td>
+<td>drill.exec.http.profile.warning.scan.wait.min</td>
+<td>Sets a minimum threshold ratio for the scan operator to wait. When the
average wait time exceeds the processing time the Drill Web UI displays the
warning. Default is 60 seconds.</td>
+</tr>
+</tbody></table>
+
+<h3 id="configuring-warning-threshold-options">Configuring Warning Threshold
Options</h3>
+
+<p>You can configure thresholds for the warnings through configuration options
in the drill-override.conf file, as shown: </p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">http:
{
+ profile.warning: {
+ progress.threshold: 300,
+ time.skew: {
+ min: 2,
+ ratio: {
+ process: 2
+ wait: 2
+ }
+ },
+ scan.wait.min: 60
+ },
+ ...
+}
+</code></pre></div>
+<p>You must restart Drillbits after you modify drill-override.conf.</p>
+
+<p>The following sections describe the Fragment Profiles and Operator Profiles
sections of the Drill Web UI in more detail. </p>
<h2 id="fragment-profiles">Fragment Profiles</h2>
diff --git a/docs/rest-api-introduction/index.html
b/docs/rest-api-introduction/index.html
index 52fb521..f48bda0 100644
--- a/docs/rest-api-introduction/index.html
+++ b/docs/rest-api-introduction/index.html
@@ -1310,7 +1310,7 @@
</div>
- Dec 8, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1378,7 +1378,8 @@
<ul>
<li>queryType--SQL, PHYSICAL, or LOGICAL are valid types. Use only
"SQL". Other types are for internal use only.<br></li>
-<li>query--A SQL query that runs in Drill.</li>
+<li>query--A SQL query that runs in Drill.<br></li>
+<li>autoLimit--Limits the number of rows returned from the result set. (Drill
1.16+)</li>
</ul>
<p><strong>Request Body</strong></p>
@@ -1388,7 +1389,7 @@
}
</code></pre></div>
<p><strong>Example</strong></p>
-<div class="highlight"><pre><code class="language-text" data-lang="text"> curl
-X POST -H "Content-Type: application/json" -d
'{"queryType":"SQL", "query": "select *
from dfs.`/Users/joe-user/apache-drill-1.4.0/sample-data/donuts.json` where
name= \u0027Cake\u0027"}' http://localhost:8047/query.json
+<div class="highlight"><pre><code class="language-text" data-lang="text"> curl
-X POST -H "Content-Type: application/json" -d
'{"queryType":"SQL", "query": "select *
from dfs.`/Users/joe-user/apache-drill-1.4.0/sample-data/donuts.json` where
name= \u0027Cake\u0027", "autoLimit":1}'
http://localhost:8047/query.json
</code></pre></div>
<p><strong>Response Body</strong></p>
<div class="highlight"><pre><code class="language-text" data-lang="text"> {
diff --git a/docs/starting-the-web-ui/index.html
b/docs/starting-the-web-ui/index.html
index 28a9012..3f67398 100644
--- a/docs/starting-the-web-ui/index.html
+++ b/docs/starting-the-web-ui/index.html
@@ -1308,7 +1308,7 @@
</div>
- Dec 28, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1325,21 +1325,31 @@
<li><a
href="/docs/planning-and-execution-options/#setting-options-from-the-drill-web-ui">Set
configuration options</a><br></li>
</ul>
-<p>Starting in Drill 1.15, you can use a Meta+Enter key combination instead of
clicking the Submit button to submit queries through the query editor (Query
page) in Drill Web UI. On Mac keyboards, the combination is Ctrl+Meta or
Ctrl+Enter. On Windows and Linux, the combination is Ctrl+Enter; however, on
Linux, if you mapped the meta key to another physical key on the keyboard, use
that key + Enter. </p>
-
<h2 id="accessing-the-web-ui">Accessing the Web UI</h2>
-<p>To access the Drill Web UI, enter the URL appropriate for your Drill
configuration. The following list describes the URLs for various Drill
configurations: </p>
+<p>To access the Drill Web UI, enter
<code>http(s)://<drill-hostname-or-ip-address>:8047</code> in your
browser's address bar. Note that Drill must be running on the node in order
to access the Drill Web UI. </p>
+
+<p>The following list describes the URLs for various Drill configurations: </p>
<ul>
-<li><code>http://<IP address or host name>:8047</code><br>
+<li><code>http://<drill-hostname-or-ip-address>:8047</code><br>
Use this URL when <a
href="/docs/configuring-web-console-and-rest-api-security/#https-support">HTTPS
support</a> is disabled (the default).</li>
-<li><code>https://<IP address or host name>:8047</code><br>
+<li><code>https://<drill-hostname-or-ip-address>:8047</code><br>
Use this URL when HTTPS support is enabled.<br></li>
<li><code>http://localhost:8047</code><br>
-Use this URL when running Drill in embedded mode (./drill-embedded).</li>
+Use this URL when running Drill in embedded mode (./drill-embedded).<br></li>
</ul>
+<h2 id="running-queries-from-the-web-ui">Running Queries from the Web UI</h2>
+
+<p>To run a query in the Web UI, click Query in the toolbar to access the
Query page. Enter your query in the query editor and click Submit or press
Ctrl+Enter to submit the query. </p>
+
+<p>Starting in Drill 1.15, you can use a Meta+Enter key combination to submit
queries through the query editor. On Mac keyboards, the combination is
Ctrl+Meta or Ctrl+Enter. On Windows and Linux, the combination is Ctrl+Enter;
however, on Linux, if you mapped the meta key to another physical key on the
keyboard, use that key + Enter.</p>
+
+<p>Starting in Drill 1.16, a Query Submitted pop-up window appears when you
submit a query.<br>
+<img src="https://i.imgur.com/MOcBlZo.png"; alt=""><br>
+The pop-up serves as an indicator that a query is in progress and prevents any
further action until the query returns results. The pop-up includes a Check
Status button that links to the Profiles page. If needed, you can <a
href="/docs/monitoring-and-canceling-queries-in-the-drill-web-ui/">cancel the
query from the Profiles page</a>. </p>
+
<h2 id="web-ui-security">Web UI Security</h2>
<p>If <a href="/docs/configuring-user-authentication/">user authentication</a>
is not enabled, all the Web UI controls appear to users as well as
administrators: </p>
diff --git
a/docs/submitting-queries-from-the-rest-api-when-impersonation-is-enabled-and-authentication-is-disabled/index.html
b/docs/submitting-queries-from-the-rest-api-when-impersonation-is-enabled-and-authentication-is-disabled/index.html
index 5360cbe..6adc98b 100644
---
a/docs/submitting-queries-from-the-rest-api-when-impersonation-is-enabled-and-authentication-is-disabled/index.html
+++
b/docs/submitting-queries-from-the-rest-api-when-impersonation-is-enabled-and-authentication-is-disabled/index.html
@@ -1310,7 +1310,7 @@
</div>
- Dec 8, 2018
+ Apr 18, 2019
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1326,7 +1326,7 @@
<h2 id="drill-web-ui">Drill Web UI</h2>
-<p>You can submit a query through the Query page in the Drill Web UI after
entering a valid username in the Username field. The Drill Web UI is accessible
through the URL http(s)://<ip-address>:8047.</p>
+<p>You can submit a query through the Query page in the Drill Web UI after
entering a valid username in the Username field. The Drill Web UI is accessible
through the URL <code>http(s)://<drill-hostname>:8047</code>.</p>
<p>To re-run a query from the Profiles page in the Drill Web UI, you must
submit a username prior to re-running the query.</p>
diff --git a/feed.xml b/feed.xml
index 3454a36..a8cabe0 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>/</link>
<atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Tue, 16 Apr 2019 13:44:35 -0700</pubDate>
- <lastBuildDate>Tue, 16 Apr 2019 13:44:35 -0700</lastBuildDate>
+ <pubDate>Thu, 18 Apr 2019 12:19:09 -0700</pubDate>
+ <lastBuildDate>Thu, 18 Apr 2019 12:19:09 -0700</lastBuildDate>
<generator>Jekyll v2.5.2</generator>
<item>
![https://i.imgur.com/MnLY75q.png"](https://i.imgur.com/MnLY75q.png"){kind=link}
![https://i.imgur.com/91ubjpb.png"](https://i.imgur.com/91ubjpb.png"){kind=link}
![https://i.imgur.com/SQH3YNT.png"](https://i.imgur.com/SQH3YNT.png"){kind=link}
![https://i.imgur.com/WMij8gQ.png"](https://i.imgur.com/WMij8gQ.png"){kind=link}
![https://i.imgur.com/7nF0RBq.png"](https://i.imgur.com/7nF0RBq.png"){kind=link}
![https://i.imgur.com/eYn22NL.png"](https://i.imgur.com/eYn22NL.png"){kind=link}
![https://i.imgur.com/L4Yx666.png"](https://i.imgur.com/L4Yx666.png"){kind=link}
![https://i.imgur.com/IVA2fKG.png"](https://i.imgur.com/IVA2fKG.png"){kind=link}
![https://i.imgur.com/rnT6Uq5.png"](https://i.imgur.com/rnT6Uq5.png"){kind=link}
![https://i.imgur.com/hxwsiaA.png"](https://i.imgur.com/hxwsiaA.png"){kind=link}
![https://i.imgur.com/HHA5CkV.png"](https://i.imgur.com/HHA5CkV.png"){kind=link}
![https://i.imgur.com/MOcBlZo.png"](https://i.imgur.com/MOcBlZo.png"){kind=link}