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 726b2f5 Doc updates per DRILL-6834 and DRILL-6787
726b2f5 is described below
commit 726b2f533c4bc9dd125f6c9b3f1198fcbd902a3f
Author: Bridget Bevens <[email protected]>
AuthorDate: Mon Dec 10 18:55:13 2018 -0800
Doc updates per DRILL-6834 and DRILL-6787
---
.../index.html | 26 ++++++++++++++--------
docs/interfaces-introduction/index.html | 9 ++++++--
feed.xml | 4 ++--
3 files changed, 26 insertions(+), 13 deletions(-)
diff --git
a/docs/configuring-drill-to-use-spnego-for-http-authentication/index.html
b/docs/configuring-drill-to-use-spnego-for-http-authentication/index.html
index c3f5157..689af94 100644
--- a/docs/configuring-drill-to-use-spnego-for-http-authentication/index.html
+++ b/docs/configuring-drill-to-use-spnego-for-http-authentication/index.html
@@ -1274,7 +1274,7 @@
</div>
- Dec 8, 2018
+ Dec 11, 2018
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1301,7 +1301,7 @@
<p>SPNEGO authentication for Drill requires the following: </p>
<ul>
-<li>Drill 1.13 installed on each node.<br></li>
+<li>Drill 1.13 or later installed on each node.<br></li>
<li>To use SPNEGO, you must have a working Kerberos infrastructure, which
Drill does not provide.<br></li>
<li>You must be working in a Linux-based or Windows Active Directory (AD)
Kerberos environment with secure clusters and have a Drill server configured
for Kerberos.<br></li>
<li>Kerberos principal and keytab on each Drillbit (web server) that will use
SPNEGO for authentication.<br></li>
@@ -1327,10 +1327,10 @@
<ul>
<li><p>To enable SPNEGO, add the following configuration to
<code>drill-override.conf</code>: </p>
<div class="highlight"><pre><code class="language-text" data-lang="text">
drill.exec.http: {
- spnego.auth.principal:"HTTP/hostname@realm",
- spnego.auth.keytab:"path/to/keytab",
- auth.mechanisms: [“SPNEGO”]
- }
+ auth.spnego.principal:"HTTP/hostname@realm",
+ auth.spnego.keytab:"path/to/keytab",
+ auth.mechanisms: [“SPNEGO”]
+ }
//The default authentication mechanism is “FORM”.
</code></pre></div></li>
@@ -1377,10 +1377,18 @@
<h3 id="chrome">Chrome</h3>
-<p>For MacOS or Linux, add the <code>--auth-server-whitelist</code> parameter
to the <code>google-chrome</code> command. For example, to run Chrome from a
Linux prompt, run the <code>google-chrome</code> command, as follows:</p>
-<div class="highlight"><pre><code class="language-text" data-lang="text">
google-chrome --auth-server-whitelist = "hostname/domain"
- Example: google-chrome --auth-server-whitelist = "example.QA.LAB"
+<p>For Linux, add the <code>--auth-server-whitelist</code> parameter to the
<code>google-chrome</code> command. For example, to run Chrome from a Linux
prompt, run the <code>google-chrome</code> command, as follows: </p>
+<div class="highlight"><pre><code class="language-text"
data-lang="text">google-chrome --auth-server-whitelist="domain"
+
+example: google-chrome --auth-server-whitelist="machine.example.com"
+example: google-chrome --auth-server-whitelist="*.example.com"
+</code></pre></div>
+<p>For MacOS, use the following directories: </p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">cd
/Applications/Google Chrome.app/Contents/MacOS
+./"Google Chrome" --auth-server-whitelist="*.example.com"
</code></pre></div>
+<p><strong>Note:</strong> The URL given to Chrome to access the Web UI should
match the domain specified in <code>auth-server-whitelist</code>. If the domain
is used in <code>auth-server-whitelist</code>, use the domain with Chrome. If
the IP address is used in <code>auth-server-whitelist</code>, use the IP
address with Chrome. </p>
+
<h3 id="safari">Safari</h3>
<p>No configuration is required for Safari. Safari automatically authenticates
using SPNEGO when requested by the server. </p>
diff --git a/docs/interfaces-introduction/index.html
b/docs/interfaces-introduction/index.html
index 1ebc146..e3a3bfc 100644
--- a/docs/interfaces-introduction/index.html
+++ b/docs/interfaces-introduction/index.html
@@ -1272,7 +1272,7 @@
</div>
- Dec 8, 2018
+ Dec 11, 2018
<link href="/css/docpage.css" rel="stylesheet" type="text/css">
@@ -1284,12 +1284,17 @@
<li>Drill shell</li>
<li>Drill Web UI</li>
<li><a href="/docs/installing-the-odbc-driver/">ODBC</a>*</li>
-<li><a href="/docs/using-jdbc-with-squirrel-on-windows/">JDBC</a></li>
+<li><a href="/docs/using-jdbc-with-squirrel-on-windows/">JDBC</a>**</li>
<li>C++ API</li>
</ul>
<p>*Apache Drill does not have an open source ODBC driver. However, MapR
provides an <a href="https://package.mapr.com/tools/MapR-ODBC/MapR_Drill/";>ODBC
driver</a> developed specifically for connecting Apache Drill to BI tools. MapR
also provides a <a
href="https://package.mapr.com/tools/MapR-JDBC/MapR_Drill/";>JDBC driver</a>.
</p>
+<p>**By default, Drill returns a result set when you issue DDL statements,
such as CTAS and CREATE VIEW. If the client tool from which you connect to
Drill (via JDBC) does not expect a result set when you issue DDL statements,
set the <code>exec.return_result_set_for_ddl</code> option (Drill 1.15 and
later) to false, as shown, to prevent the client from canceling queries: </p>
+<div class="highlight"><pre><code class="language-text" data-lang="text">SET
`exec.return_result_set_for_ddl` = false
+</code></pre></div>
+<p>When set to false, Drill returns the affected rows count, and the result
set is null. </p>
+
<h2 id="using-odbc-to-access-apache-drill-from-bi-tools">Using ODBC to Access
Apache Drill from BI Tools</h2>
<p>MapR provides an ODBC driver that connects Windows, Mac OS X, and Linux to
Apache Drill and BI tools. Install the latest version of Apache Drill with the
latest version of the MapR Drill ODBC driver. </p>
diff --git a/feed.xml b/feed.xml
index 8aad132..4954823 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>Mon, 10 Dec 2018 16:34:32 -0800</pubDate>
- <lastBuildDate>Mon, 10 Dec 2018 16:34:32 -0800</lastBuildDate>
+ <pubDate>Mon, 10 Dec 2018 18:52:58 -0800</pubDate>
+ <lastBuildDate>Mon, 10 Dec 2018 18:52:58 -0800</lastBuildDate>
<generator>Jekyll v2.5.2</generator>
<item>
