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 d04d112 doc edits and updates
d04d112 is described below
commit d04d11217e018d5c7ee4b04da6cee7c120d9941e
Author: Bridget Bevens <[email protected]>
AuthorDate: Mon Jan 7 15:18:15 2019 -0800
doc edits and updates
---
_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md | 6 +++---
_docs/query-data/070-query-sys-tbl.md | 4 ++--
_docs/rn/001-1.15.0-rn.md | 6 +++---
_docs/sql-reference/sql-commands/010-set.md | 6 +++---
_docs/sql-reference/sql-commands/030-create-table-as.md | 6 +++---
_docs/sql-reference/sql-commands/034-create-function-using-jar.md | 6 +++---
_docs/sql-reference/sql-commands/050-create-view.md | 6 +++---
_docs/sql-reference/sql-commands/054-drop-function-using-jar.md | 6 +++---
_docs/sql-reference/sql-commands/055-drop-table.md | 6 +++---
_docs/sql-reference/sql-commands/056-drop-view.md | 6 +++---
_docs/sql-reference/sql-commands/120-use.md | 6 +++---
11 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
index 0ec62c2..40958aa 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-11
+date: 2019-01-07
parent: "ODBC/JDBC Interfaces"
---
You can connect to Apache Drill through the following interfaces:
@@ -13,9 +13,9 @@ You can connect to Apache Drill through the following
interfaces:
*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 to false, as shown, to prevent the
client from canceling queries:
+**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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the result set
is null.
diff --git a/_docs/query-data/070-query-sys-tbl.md
b/_docs/query-data/070-query-sys-tbl.md
index 5af7b78..aca5800 100644
--- a/_docs/query-data/070-query-sys-tbl.md
+++ b/_docs/query-data/070-query-sys-tbl.md
@@ -1,6 +1,6 @@
---
title: "Querying System Tables"
-date: 2018-12-10
+date: 2019-01-07
parent: "Query Data"
---
@@ -234,7 +234,7 @@ The connections table provides the following information
about the connection to
+---------------------------------------+----------------------------------------------------------------------------------+
| queryId |
json |
+---------------------------------------+----------------------------------------------------------------------------------+
- | 23f4e2a7-5d60-a766-0b03-d7a03e99033e |
{"id":{"part1":2590944894098909030,"part2":793715042592293694},"type":1,"start":1544232280280,"end":1544232280309,"query":"SELECT
* FROM profiles_json LIMIT 0","plan":"00-00 Screen : rowType =
RecordType(VARCHAR(65536) queryId, VARCHAR(65536) json): rowcount = 1.0,
cumulative cost = {1.1 rows, 2.1 cpu, 1.0 io, 0.0 network, 0.0 memory}, id =
2115\n00-01 Project(queryId=[$0], json=[$1]) : rowType =
RecordType(VARCHAR(65536) queryId, VARCH [...]
+ | 23f4e2a7-5d60-a766-0b03-d7a03e99033e |
{"id":{"part1":2590944894098909030,"part2":793715042592293694},"type":1,"start":1544232280280,"end":1544232280309,"query":"SELECT
* FROM profiles_json LIMIT 0","plan":"00-00 Screen : rowType =
RecordType(VARCHAR(65536) queryId, VARCHAR(65536) json): rowcount = 1.0,
cumulative cost = {1.1 rows, 2.1 cpu, 1.0 io, 0.0 network, 0.0 memory}, id =
2115\n00-01 Project(queryId=[$0], json=[$1]) : rowType =
RecordType(VARCHAR(65536) queryId, VARCH [...]
+---------------------------------------+----------------------------------------------------------------------------------+
The profiles_json table provides the query profile in JSON format for all
queries, by queryID.
diff --git a/_docs/rn/001-1.15.0-rn.md b/_docs/rn/001-1.15.0-rn.md
index a5c5ab7..bae5b9f 100644
--- a/_docs/rn/001-1.15.0-rn.md
+++ b/_docs/rn/001-1.15.0-rn.md
@@ -19,16 +19,16 @@ This release of Drill provides the following new features
and improvements:
- New [system options
table]({{site.baseurl}}/docs/querying-system-tables/#querying-the-options-table).
([DRILL-6684](https://issues.apache.org/jira/browse/DRILL-6684))
- Support for
[TIMESTAMPADD]({{site.baseurl}}/docs/date-time-functions-and-arithmetic/#timestampadd)
and
[TIMESTAMPDIFF]({{site.baseurl}}/docs/date-time-functions-and-arithmetic/#timestampdiff)
datetime functions.
([DRILL-3610](https://issues.apache.org/jira/browse/DRILL-3610))
- Ability to [secure znodes with custom
ACLs]({{site.baseurl}}/docs/configuring-custom-acls-to-secure-znodes/) (Access
Control Lists) ([DRILL-5671](https://issues.apache.org/jira/browse/DRILL-5671)).
-- All cast and data type conversion functions return null for an empty string
('') when the `drill.exec.functions.cast_empty_string_to_null` option is
enabled. ([DRILL-6817](https://issues.apache.org/jira/browse/DRILL-6817))
+- All [cast and data type conversion
functions]({{site.baseurl}}/docs/data-type-conversion/) return null for an
empty string ('') when the `drill.exec.functions.cast_empty_string_to_null`
option is enabled.
([DRILL-6817](https://issues.apache.org/jira/browse/DRILL-6817))
- [Storage plugin names are
case-insensitive]({{site.baseurl}}/docs/lexical-structure/).
([DRILL-6492](https://issues.apache.org/jira/browse/DRILL-6492))
- Ability to access your AWS access key ID and secret access key using the
Credential Provider API for the [S3 storage
plugin]({{site.baseurl}}/docs/s3-storage-plugin/#using-an-external-provider-for-credentials).
([DRILL-6662](https://issues.apache.org/jira/browse/DRILL-6662))
- [Upgrade to SQLLine 1.6]({{site.baseurl}}/docs/configuring-the-drill-shell/)
includes the ability to add custom configuration.
([DRILL-3853](https://issues.apache.org/jira/browse/DRILL-3853))
- [New SQLLine connection
parameters]({{site.baseurl}}/docs/configuring-the-drill-shell/#sqlline-connection-parameters)
([DRILL-3933](https://issues.apache.org/jira/browse/DRILL-3933))
-- New option, `exec.return_result_set_for_ddl`, prevents Drill from returning
a result set for DDL statements when set to "false." Useful for clients tools
that connect to Drill (via JDBC) if they do not expect a result set.
([DRILL-6834](https://issues.apache.org/jira/browse/DRILL-6834))
+- New option, `exec.query.return_result_set_for_ddl`, [prevents Drill from
returning a result set for DDL
statements]({{site.baseurl}}/docs/interfaces-introduction/) when set to
"false." Useful for clients tools that connect to Drill (via JDBC) if they do
not expect a result set.
([DRILL-6834](https://issues.apache.org/jira/browse/DRILL-6834))
- [Parquet filter pushdown for VARCHAR and DECIMAL data
types]({{site.baseurl}}/docs/parquet-filter-pushdown/#parquet-filter-pushdown-for-varchar-and-decimal-data-types)
([DRILL-6744](https://issues.apache.org/jira/browse/DRILL-6744))
- Improved query performance with the [semi-join
functionality](https://drill.apache.org/docs/sort-based-and-hash-based-memory-constrained-operators/#disabling-the-hash-operators)
inside the Hash-Join operator.
([DRILL-6735](https://issues.apache.org/jira/browse/DRILL-6735))
- [Lateral join](https://drill.apache.org/docs/lateral-join/) functionality is
enabled by default.
([DRILL-6729](https://issues.apache.org/jira/browse/DRILL-6729))
-- Support JPPD (Join Predicate Push Down).
([DRILL-6385](https://issues.apache.org/jira/browse/DRILL-6385))
+- Support JPPD (Join Predicate Push Down).
[DRILL-6385](https://issues.apache.org/jira/browse/DRILL-6385)
- Multiple [Web UI
improvements]({{site.baseurl}}/docs/planning-and-execution-options/#setting-options-from-the-drill-web-ui)
to simplify the use of options and submit queries, including:
- Search field
- Quick Filters
([DRILL-5735](https://issues.apache.org/jira/browse/DRILL-5735))
diff --git a/_docs/sql-reference/sql-commands/010-set.md
b/_docs/sql-reference/sql-commands/010-set.md
index a8b81c4..f4ae32a 100644
--- a/_docs/sql-reference/sql-commands/010-set.md
+++ b/_docs/sql-reference/sql-commands/010-set.md
@@ -1,6 +1,6 @@
---
title: "SET"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
Starting in Drill 1.3, the SET command replaces the ALTER SESSION SET command.
The SET command changes a system setting for the duration of a session. Session
level settings override system level settings.
@@ -22,9 +22,9 @@ or float. Use the appropriate value type for each option that
you set.
## Usage Notes
-- By default, Drill returns a result set when you issue DDL statements, such
as SET. 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 to false, as shown, to prevent the
client from canceling queries:
+- By default, Drill returns a result set when you issue DDL statements, such
as SET. 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the
result set is null.
diff --git a/_docs/sql-reference/sql-commands/030-create-table-as.md
b/_docs/sql-reference/sql-commands/030-create-table-as.md
index 48383d0..446886b 100644
--- a/_docs/sql-reference/sql-commands/030-create-table-as.md
+++ b/_docs/sql-reference/sql-commands/030-create-table-as.md
@@ -1,6 +1,6 @@
---
title: "CREATE TABLE AS (CTAS)"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
Use the CREATE TABLE AS (CTAS) command to create tables in Drill.
@@ -21,9 +21,9 @@ A SELECT statement that needs to include aliases for
ambiguous column names, suc
## Usage Notes
-- By default, Drill returns a result set when you issue DDL statements, such
as CTAS. 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 to false, as shown, to prevent the
client from canceling queries:
+- By default, Drill returns a result set when you issue DDL statements, such
as CTAS. 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the
result set is null.
diff --git a/_docs/sql-reference/sql-commands/034-create-function-using-jar.md
b/_docs/sql-reference/sql-commands/034-create-function-using-jar.md
index 5c8e8fb..dba20b9 100644
--- a/_docs/sql-reference/sql-commands/034-create-function-using-jar.md
+++ b/_docs/sql-reference/sql-commands/034-create-function-using-jar.md
@@ -1,6 +1,6 @@
---
title: "CREATE FUNCTION USING JAR"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
The CREATE FUNCTION USING JAR command registers UDFs in Drill. See [Dynamic
UDFs]({{site.baseurl}}/docs/dynamic-udfs/) for more information.
@@ -18,9 +18,9 @@ The name of the JAR file that contains the UDFs.
## Usage Notes
- Before you issue the CREATE FUNCTION USING JAR command, you must Copy the
UDF source and binary JAR files to the DFS staging directory. When you issue
this command, Drill uses the JAR file name to register the JAR name in the
Dynamic UDF registry ([persistent
store]({{site.baseurl}}/docs/persistent-configuration-storage/)) and then
copies the source and binary JAR files to the local UDF directory on each
drillbit upon request.
-- By default, Drill returns a result set when you issue DDL statements, such
as CREATE FUNCTION USING JAR. 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 to false, as shown, to prevent
the client from canceling queries:
+- By default, Drill returns a result set when you issue DDL statements, such
as CREATE FUNCTION USING JAR. 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.query.return_result_set_for_ddl` option to false, as shown, to
prevent the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the
result set is null.
diff --git a/_docs/sql-reference/sql-commands/050-create-view.md
b/_docs/sql-reference/sql-commands/050-create-view.md
index c83b800..ddfd50e 100644
--- a/_docs/sql-reference/sql-commands/050-create-view.md
+++ b/_docs/sql-reference/sql-commands/050-create-view.md
@@ -1,6 +1,6 @@
---
title: "CREATE VIEW"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
The CREATE VIEW command creates a virtual structure for the result set of a
@@ -43,9 +43,9 @@ A SELECT statement that defines the columns and rows in the
view.
## Usage Notes
-By default, Drill returns a result set when you issue DDL statements, such as
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 to false, as shown, to prevent the
client from canceling queries:
+By default, Drill returns a result set when you issue DDL statements, such as
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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the result set
is null.
diff --git a/_docs/sql-reference/sql-commands/054-drop-function-using-jar.md
b/_docs/sql-reference/sql-commands/054-drop-function-using-jar.md
index 633cdd7..9780765 100644
--- a/_docs/sql-reference/sql-commands/054-drop-function-using-jar.md
+++ b/_docs/sql-reference/sql-commands/054-drop-function-using-jar.md
@@ -1,6 +1,6 @@
---
title: "DROP FUNCTION USING JAR"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
@@ -21,9 +21,9 @@ The name of the JAR file that contains the UDFs.
- When you issue the DROP FUNCTION USING JAR command, Drill unregisters the
UDFs based on the JAR file name and removes the JAR file from the UDF
directory. Drill deletes all UDFs associated with the JAR file from the Dynamic
UDF registry ([persistent
store]({{site.baseurl}}/docs/persistent-configuration-storage/)). Drill returns
a message with the list of unregistered UDFs.
-- By default, Drill returns a result set when you issue DDL statements, such
as DROP FUNCTION USING JAR. 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 to false, as shown, to prevent the
client from canceling queries:
+- By default, Drill returns a result set when you issue DDL statements, such
as DROP FUNCTION USING JAR. 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the
result set is null.
diff --git a/_docs/sql-reference/sql-commands/055-drop-table.md
b/_docs/sql-reference/sql-commands/055-drop-table.md
index d306b71..822a2b8 100644
--- a/_docs/sql-reference/sql-commands/055-drop-table.md
+++ b/_docs/sql-reference/sql-commands/055-drop-table.md
@@ -1,6 +1,6 @@
---
title: "DROP TABLE"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
@@ -24,9 +24,9 @@ A unique directory or file name, optionally prefaced by a
storage plugin name, s
## Usage Notes
-By default, Drill returns a result set when you issue DDL statements, such as
DROP TABLE. 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 to false, as shown, to prevent the
client from canceling queries:
+By default, Drill returns a result set when you issue DDL statements, such as
DROP TABLE. 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the result set
is null.
diff --git a/_docs/sql-reference/sql-commands/056-drop-view.md
b/_docs/sql-reference/sql-commands/056-drop-view.md
index f40b4c7..d8d878d 100644
--- a/_docs/sql-reference/sql-commands/056-drop-view.md
+++ b/_docs/sql-reference/sql-commands/056-drop-view.md
@@ -1,6 +1,6 @@
---
title: "DROP VIEW"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
@@ -25,9 +25,9 @@ A unique directory or file name, optionally prefaced by a
storage plugin name, s
## Usage Notes
-- By default, Drill returns a result set when you issue DDL statements, such
as DROP 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 to false, as shown, to prevent the
client from canceling queries:
+- By default, Drill returns a result set when you issue DDL statements, such
as DROP 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the
result set is null.
diff --git a/_docs/sql-reference/sql-commands/120-use.md
b/_docs/sql-reference/sql-commands/120-use.md
index 7ce750a..9c0d602 100644
--- a/_docs/sql-reference/sql-commands/120-use.md
+++ b/_docs/sql-reference/sql-commands/120-use.md
@@ -1,6 +1,6 @@
---
title: "USE"
-date: 2018-12-11
+date: 2019-01-07
parent: "SQL Commands"
---
The USE command changes the schema context to the specified schema. When you
@@ -57,9 +57,9 @@ SCHEMAS to see a list of the configured storage plugins and
workspaces.
***
**NOTE**
-By default, Drill returns a result set when you issue DDL statements, such as
USE. 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 to false, as shown, to prevent the
client from canceling queries:
+By default, Drill returns a result set when you issue DDL statements, such as
USE. 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.query.return_result_set_for_ddl` option to false, as shown, to prevent
the client from canceling queries:
- SET `exec.return_result_set_for_ddl` = false
+ SET `exec.query.return_result_set_for_ddl` = false
//This option is available in Drill 1.15 and later.
When set to false, Drill returns the affected rows count, and the result set
is null.
