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 1d27a5b drill 1.15 doc updates
1d27a5b is described below
commit 1d27a5be6bef4077d1cfd5df431404b6ab966120
Author: Bridget Bevens <[email protected]>
AuthorDate: Tue Dec 11 13:24:57 2018 -0800
drill 1.15 doc updates
---
.../010-interfaces-introduction.md | 3 +-
_docs/sample-datasets/001-aol.md | 50 ----------------------
.../sample-datasets/{002-enron.md => 001-enron.md} | 0
.../{003-wikipedia.md => 002-wikipedia.md} | 0
_docs/sql-reference/sql-commands/010-set.md | 6 +++
.../sql-commands/030-create-table-as.md | 23 +++++-----
.../sql-commands/034-create-function-using-jar.md | 13 ++++--
.../sql-reference/sql-commands/050-create-view.md | 11 ++++-
.../sql-commands/054-drop-function-using-jar.md | 14 ++++--
_docs/sql-reference/sql-commands/055-drop-table.md | 10 ++++-
_docs/sql-reference/sql-commands/056-drop-view.md | 15 +++++--
_docs/sql-reference/sql-commands/120-use.md | 14 +++++-
12 files changed, 81 insertions(+), 78 deletions(-)
diff --git a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
index f03cf16..0ec62c2 100644
--- a/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
+++ b/_docs/odbc-jdbc-interfaces/010-interfaces-introduction.md
@@ -13,9 +13,10 @@ 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 (Drill 1.15 and later) 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.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
+ //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/sample-datasets/001-aol.md b/_docs/sample-datasets/001-aol.md
deleted file mode 100644
index d9b8eed..0000000
--- a/_docs/sample-datasets/001-aol.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "AOL Search"
-date: 2016-01-06
-redirect_to:
- - http://gregsadetsky.com/aol-data
-parent: "Sample Datasets"
----
-## Quick Stats
-
-The [AOL Search dataset](http://en.wikipedia.org/wiki/AOL_search_data_leak) is
-a collection of real query log data that is based on real users.
-
-## The Data Source
-
-The dataset consists of 20M Web queries from 650k users over a period of three
-months, 440MB in total and available [for
-download](http://gregsadetsky.com/aol-data/). The format used in
-the dataset is:
-
- AnonID, Query, QueryTime, ItemRank, ClickURL
-
-... with:
-
- * AnonID, an anonymous user ID number.
- * Query, the query issued by the user, case shifted with most punctuation
removed.
- * QueryTime, the time at which the query was submitted for search.
- * ItemRank, if the user clicked on a search result, the rank of the item on
which they clicked is listed.
- * [ClickURL](http://www.dietkart.com/), if the user clicked on a search
result, the domain portion of the URL in the clicked result is listed.
-
-Each line in the data represents one of two types of events
-
- * A query that was NOT followed by the user clicking on a result item.
- * A click through on an item in the result list returned from a query.
-
-In the first case (query only) there is data in only the first three columns,
-in the second case (click through), there is data in all five columns. For
-click through events, the query that preceded the click through is included.
-Note that if a user clicked on more than one result in the list returned from
-a single query, there will be TWO lines in the data to represent the two
-events.
-
-## The Queries
-
-Interesting queries, for example
-
- * Users querying for topic X
- * Users that click on the first (second, third) ranked item
- * TOP 10 domains searched
- * TOP 10 domains clicked at
-
diff --git a/_docs/sample-datasets/002-enron.md
b/_docs/sample-datasets/001-enron.md
similarity index 100%
rename from _docs/sample-datasets/002-enron.md
rename to _docs/sample-datasets/001-enron.md
diff --git a/_docs/sample-datasets/003-wikipedia.md
b/_docs/sample-datasets/002-wikipedia.md
similarity index 100%
rename from _docs/sample-datasets/003-wikipedia.md
rename to _docs/sample-datasets/002-wikipedia.md
diff --git a/_docs/sql-reference/sql-commands/010-set.md
b/_docs/sql-reference/sql-commands/010-set.md
index c852ee9..a8b81c4 100644
--- a/_docs/sql-reference/sql-commands/010-set.md
+++ b/_docs/sql-reference/sql-commands/010-set.md
@@ -22,6 +22,12 @@ 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:
+
+ SET `exec.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.
- You can still use the ALTER SESSION SET command; however, ALTER SESSION is
now just an alias for the SET command.
- Use the SET command to change Drill query planning and execution options per
session in a cluster.
- The options that you set only apply to queries that run during the current
Drill connection.
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 6866988..3be002d 100644
--- a/_docs/sql-reference/sql-commands/030-create-table-as.md
+++ b/_docs/sql-reference/sql-commands/030-create-table-as.md
@@ -1,9 +1,9 @@
---
title: "CREATE TABLE AS (CTAS)"
-date: 2017-08-09 22:58:36 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
-Use the CTAS command to create tables in Drill.
+Use the CTAS (CREATE TABLE AS) command to create tables in Drill.
## Syntax
@@ -21,11 +21,16 @@ A SELECT statement that needs to include aliases for
ambiguous column names, suc
## Usage Notes
-- You can use the [PARTITION BY]({{site.baseurl}}/docs/partition-by-clause)
clause in a CTAS command.
+- 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:
+
+ SET `exec.return_result_set_for_ddl` = false
+ //This option is available in Drill 1.15 and later.
-- Drill writes files having names, such as 0_0_0.parquet, to the directory
named in the CTAS command or to the workspace that is in use when you run the
CTAS statement. You query the directory as you would query a table.
+ When set to false, Drill returns the affected rows count, and the
result set is null.
+- You can use the [PARTITION BY]({{site.baseurl}}/docs/partition-by-clause)
clause in a CTAS command.
+- Drill writes files having names, such as 0_0_0.parquet, to the directory
named in the CTAS command or to the workspace that is in use when you run the
CTAS statement. You query the directory as you would query a table.
- The following command writes Parquet data from `nation.parquet`,
installed with Drill, to the `/tmp/name_key` directory.
@@ -42,19 +47,13 @@ A SELECT statement that needs to include aliases for
ambiguous column names, suc
- This example writes a JSON table to the `/tmp/by_yr` directory that
contains [Google Ngram
data]({{site.baseurl}}/docs/partition-by-clause/#partioning-example).
Use dfs.tmp;
- CREATE TABLE by_yr (yr, ngram, occurrances) AS SELECT COLUMNS[0]
ngram, COLUMNS[1] yr, COLUMNS[2] occurrances FROM
`googlebooks-eng-all-5gram-20120701-zo.tsv` WHERE (columns[1] = '1993');
-
-
+ CREATE TABLE by_yr (yr, ngram, occurrances) AS SELECT COLUMNS[0]
ngram, COLUMNS[1] yr, COLUMNS[2] occurrances FROM
`googlebooks-eng-all-5gram-20120701-zo.tsv` WHERE (columns[1] = '1993');
- Drill 1.11 introduces the `exec.persistent_table.umask` option, which
enables you to set permissions on tables and directories that result from
running the CTAS command. By default, the option is set to 002, which sets the
default directory permissions to 775 and default file permissions to 664. Use
the [SET]({{site.baseurl}}/docs/set/) command to change the setting for this
option at the system or session level, as shown:
ALTER SYSTEM|SESSION SET `exec.persistent_table.umask` = '000';
-
-
- - Setting the option to '000' sets the folder permissions to 777 and
the file permissions to 666. This setting gives full access to folders and
files when you create a table.
-
-
+ - Setting the option to '000' sets the folder permissions to 777 and
the file permissions to 666. This setting gives full access to folders and
files when you create a table.
## Setting the Storage Format
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 f2ece46..5c8e8fb 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: 2016-11-22 00:38:20 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
The CREATE FUNCTION USING JAR command registers UDFs in Drill. See [Dynamic
UDFs]({{site.baseurl}}/docs/dynamic-udfs/) for more information.
@@ -15,8 +15,15 @@ The CREATE FUNCTION USING JAR command supports the following
syntax:
*jar_name*
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.
+## 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:
+
+ SET `exec.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.
## Example
0: jdbc:drill:zk=local> CREATE FUNCTION USING JAR
'simple_functions.jar';
diff --git a/_docs/sql-reference/sql-commands/050-create-view.md
b/_docs/sql-reference/sql-commands/050-create-view.md
index 88d8cc4..c83b800 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: 2017-04-05 00:09:58 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
The CREATE VIEW command creates a virtual structure for the result set of a
@@ -41,7 +41,14 @@ they are derived from the query.
_query_
A SELECT statement that defines the columns and rows in the view.
-## Usage Notes
+## 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:
+
+ SET `exec.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.
### Storage
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 7792919..633cdd7 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: 2016-11-22 00:41:29 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
@@ -17,8 +17,16 @@ The DROP FUNCTION USING JAR command supports the following
syntax:
*jar_name*
The name of the JAR file that contains the UDFs.
-## Usage Notes
-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.
+## Usage Notes
+
+- 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:
+
+ SET `exec.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.
## Example
diff --git a/_docs/sql-reference/sql-commands/055-drop-table.md
b/_docs/sql-reference/sql-commands/055-drop-table.md
index 533a1e8..d306b71 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: 2016-08-04 22:01:44 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
@@ -23,7 +23,13 @@ The location of the table in subdirectories of a local or
distributed file syste
A unique directory or file name, optionally prefaced by a storage plugin name,
such as `dfs`, and a workspace, such as `tmp` using dot notation.
-## Usage Notes
+## 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:
+
+ SET `exec.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.
###Schema
* You must identify the schema in which a table exists to successfully drop
the table. You can identify the schema before dropping the table with the USE
<schema_name> command (see [USE command]({{ site.baseurl }}/docs/use/)) or when
you issue the DROP TABLE command. See [Example 1: Identifying a schema]({{
site.baseurl }}/docs/drop-table/#example-1:-identifying-a-schema).
diff --git a/_docs/sql-reference/sql-commands/056-drop-view.md
b/_docs/sql-reference/sql-commands/056-drop-view.md
index acf3139..f40b4c7 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: 2016-08-04 00:23:10 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
@@ -23,9 +23,18 @@ The location of the view in subdirectories of a local or
distributed file system
*name*
A unique directory or file name, optionally prefaced by a storage plugin name,
such as `dfs`, and a workspace, such as `tmp` using dot notation.
-## Usage Notes
+## Usage Notes
-When you drop a view, all information about the view is deleted from the
workspace in which it was created. DROP VIEW applies to the view only, not to
the underlying data sources used to create the view. However, if you drop a
view that another view is dependent on, you can no longer use the dependent
view. If the underlying tables or views change after a view is created, you may
want to drop and re-create the view. Alternatively, you can use the CREATE OR
REPLACE VIEW syntax to update t [...]
+- 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:
+
+ SET `exec.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.
+
+
+
+- When you drop a view, all information about the view is deleted from the
workspace in which it was created. DROP VIEW applies to the view only, not to
the underlying data sources used to create the view. However, if you drop a
view that another view is dependent on, you can no longer use the dependent
view. If the underlying tables or views change after a view is created, you may
want to drop and re-create the view. Alternatively, you can use the CREATE OR
REPLACE VIEW syntax to update [...]
## Example
diff --git a/_docs/sql-reference/sql-commands/120-use.md
b/_docs/sql-reference/sql-commands/120-use.md
index db2c60d..7ce750a 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: 2017-04-05 00:09:59 UTC
+date: 2018-12-11
parent: "SQL Commands"
---
The USE command changes the schema context to the specified schema. When you
@@ -53,7 +53,17 @@ table name only:
SELECT * FROM products limit 5;
Before you issue the USE command, you may want to run SHOW DATABASES or SHOW
-SCHEMAS to see a list of the configured storage plugins and workspaces.
+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:
+
+ SET `exec.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.
+***
## Example
