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 c3ad413 doc edits
c3ad413 is described below
commit c3ad413ddc733f041bfabc9fab46fd18343af1e0
Author: Bridget Bevens <[email protected]>
AuthorDate: Mon Dec 10 18:50:41 2018 -0800
doc edits
---
...-drill-to-use-spnego-for-http-authentication.md | 27 ++++++++++++++--------
.../010-interfaces-introduction.md | 10 ++++++--
2 files changed, 26 insertions(+), 11 deletions(-)
diff --git
a/_docs/configure-drill/securing-drill/091-configuring-drill-to-use-spnego-for-http-authentication.md
b/_docs/configure-drill/securing-drill/091-configuring-drill-to-use-spnego-for-http-authentication.md
index 75860cb..32d615e 100644
---
a/_docs/configure-drill/securing-drill/091-configuring-drill-to-use-spnego-for-http-authentication.md
+++
b/_docs/configure-drill/securing-drill/091-configuring-drill-to-use-spnego-for-http-authentication.md
@@ -1,6 +1,6 @@
---
title: "Configuring Drill to use SPNEGO for HTTP Authentication"
-date: 2018-12-08
+date: 2018-12-11
parent: "Securing Drill"
---
@@ -23,7 +23,7 @@ An IT administrator configures the web server (Drillbit) to
use SPNEGO for authe
SPNEGO authentication for Drill requires the following:
-- Drill 1.13 installed on each node.
+- Drill 1.13 or later installed on each node.
- To use SPNEGO, you must have a working Kerberos infrastructure, which Drill
does not provide.
- 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.
- Kerberos principal and keytab on each Drillbit (web server) that will use
SPNEGO for authentication.
@@ -50,10 +50,10 @@ To configure SPNEGO on the web server, complete the
following steps:
- To enable SPNEGO, add the following configuration to `drill-override.conf`:
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”.
@@ -98,10 +98,19 @@ To configure Firefox to use a negotiation dialog, such as
SPNEGO to authenticate
4-Set network.negotiate-auth.trusted-uris to “http://,https://”.
###Chrome
-For MacOS or Linux, add the `--auth-server-whitelist` parameter to the
`google-chrome` command. For example, to run Chrome from a Linux prompt, run
the `google-chrome` command, as follows:
+For Linux, add the `--auth-server-whitelist` parameter to the `google-chrome`
command. For example, to run Chrome from a Linux prompt, run the
`google-chrome` command, as follows:
- google-chrome --auth-server-whitelist = "hostname/domain"
- Example: google-chrome --auth-server-whitelist = "example.QA.LAB"
+ google-chrome --auth-server-whitelist="domain"
+
+ example: google-chrome --auth-server-whitelist="machine.example.com"
+ example: google-chrome --auth-server-whitelist="*.example.com"
+
+For MacOS, use the following directories:
+
+ cd /Applications/Google Chrome.app/Contents/MacOS
+ ./"Google Chrome" --auth-server-whitelist="*.example.com"
+
+**Note:** The URL given to Chrome to access the Web UI should match the domain
specified in `auth-server-whitelist`. If the domain is used in
`auth-server-whitelist`, use the domain with Chrome. If the IP address is used
in `auth-server-whitelist`, use the IP address with Chrome.
###Safari
No configuration is required for Safari. Safari automatically authenticates
using SPNEGO when requested by the server.
diff --git a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
index 9d741e4..f03cf16 100644
--- a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
+++ b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
@@ -1,6 +1,6 @@
---
title: "Interfaces Introduction"
-date: 2018-12-08
+date: 2018-12-11
parent: "ODBC/JDBC Interfaces"
---
You can connect to Apache Drill through the following interfaces:
@@ -8,11 +8,17 @@ You can connect to Apache Drill through the following
interfaces:
* Drill shell
* Drill Web UI
* [ODBC]({{ site.baseurl }}/docs/installing-the-odbc-driver/)*
- * [JDBC]({{ site.baseurl }}/docs/using-jdbc-with-squirrel-on-windows/)
+ * [JDBC]({{ site.baseurl }}/docs/using-jdbc-with-squirrel-on-windows/)**
* C++ API
*Apache Drill does not have an open source ODBC driver. However, MapR provides
an [ODBC driver](https://package.mapr.com/tools/MapR-ODBC/MapR_Drill/)
developed specifically for connecting Apache Drill to BI tools. MapR also
provides a [JDBC driver](https://package.mapr.com/tools/MapR-JDBC/MapR_Drill/).
+**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
`exec.return_result_set_for_ddl` option (Drill 1.15 and later) to false, as
shown, to prevent the client from canceling queries:
+
+ SET `exec.return_result_set_for_ddl` = false
+
+When set to false, Drill returns the affected rows count, and the result set
is null.
+
## Using ODBC to Access Apache Drill from BI Tools
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.
