You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by br...@apache.org on 2017/03/27 18:14:05 UTC
drill git commit: doc edits for 1.10
Repository: drill
Updated Branches:
refs/heads/gh-pages 062ad889a -> 479339d7f
doc edits for 1.10
Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/479339d7
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/479339d7
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/479339d7
Branch: refs/heads/gh-pages
Commit: 479339d7f0b1f0e28314065e1e821cdc816c81bc
Parents: 062ad88
Author: Bridget Bevens <bb...@maprtech.com>
Authored: Mon Mar 27 11:12:48 2017 -0700
Committer: Bridget Bevens <bb...@maprtech.com>
Committed: Mon Mar 27 11:12:48 2017 -0700
----------------------------------------------------------------------
.../data-sources-and-file-formats/040-parquet-format.md | 6 +++---
.../sql-commands/031-create-temporary-table-as.md | 12 ++++++------
blog/_posts/2017-03-15-drill-1.10-released.md | 2 +-
3 files changed, 10 insertions(+), 10 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/drill/blob/479339d7/_docs/data-sources-and-file-formats/040-parquet-format.md
----------------------------------------------------------------------
diff --git a/_docs/data-sources-and-file-formats/040-parquet-format.md b/_docs/data-sources-and-file-formats/040-parquet-format.md
index 0bf6db0..532a19f 100644
--- a/_docs/data-sources-and-file-formats/040-parquet-format.md
+++ b/_docs/data-sources-and-file-formats/040-parquet-format.md
@@ -1,6 +1,6 @@
---
title: "Parquet Format"
-date: 2017-03-13 22:49:07 UTC
+date: 2017-03-27 18:12:49 UTC
parent: "Data Sources and File Formats"
---
[Apache Parquet](http://parquet.incubator.apache.org/documentation/latest) has the following characteristics:
@@ -151,9 +151,9 @@ The first table in this section maps SQL data types to Parquet data types, limit
\* Drill 1.10 and later can implicitly interpret the Parquet INT96 type as TIMESTAMP (with standard 8 byte/millisecond precision) when the `store.parquet.int96_as_timestamp` option is enabled. In earlier versions of Drill (1.2 through 1.9) or when the `store.parquet.int96_as_timestamp` option is disabled, you must use the CONVERT_FROM function for Drill to correctly interpret INT96 values as TIMESTAMP values.
## About INT96 Support
-As of Drill 1.10, Drill can implicitly interpret the INT96 timestamp data type in Parquet files when the `store.parquet.int96_as_timestamp` option is enabled. For earlier versions of Drill, or when the `store.parquet.int96_as_timestamp` option is disabled, you must use the CONVERT_FROM function,
+As of Drill 1.10, Drill can implicitly interpret the INT96 timestamp data type in Parquet files when the `store.parquet.reader.int96_as_timestamp` option is enabled. For earlier versions of Drill, or when the `store.parquet.reader.int96_as_timestamp` option is disabled, you must use the CONVERT_FROM function,
-The `store.parquet.int96_as_timestamp` option is disabled by default. Use the [ALTER SYSTEM|SESSION SET]({{site.baseurl}}/docs/alter-system/) command to enable the option. Unnecessarily enabling this option can cause queries to fail because the CONVERT_FROM(col, 'TIMESTAMP_IMPALA') function does not work when `store.parquet.int96_as_timestamp` is enabled.
+The `store.parquet.reader.int96_as_timestamp` option is disabled by default. Use the [ALTER SYSTEM|SESSION SET]({{site.baseurl}}/docs/alter-system/) command to enable the option. Unnecessarily enabling this option can cause queries to fail because the CONVERT_FROM(col, 'TIMESTAMP_IMPALA') function does not work when `store.parquet.reader.int96_as_timestamp` is enabled.
###Using CONVERT_FROM to Interpret INT96
In earlier versions of Drill (1.2 through 1.9), you must use the CONVERT_FROM function for Drill to interpret the Parquet INT96 type. For example, to decode a timestamp from Hive or Impala, which is of type INT96, use the CONVERT_FROM function and the [TIMESTAMP_IMPALA]({{site.baseurl}}/docs/supported-data-types/#data-types-for-convert_to-and-convert_from-functions) type argument:
http://git-wip-us.apache.org/repos/asf/drill/blob/479339d7/_docs/sql-reference/sql-commands/031-create-temporary-table-as.md
----------------------------------------------------------------------
diff --git a/_docs/sql-reference/sql-commands/031-create-temporary-table-as.md b/_docs/sql-reference/sql-commands/031-create-temporary-table-as.md
index 9848c26..7755730 100644
--- a/_docs/sql-reference/sql-commands/031-create-temporary-table-as.md
+++ b/_docs/sql-reference/sql-commands/031-create-temporary-table-as.md
@@ -1,6 +1,6 @@
---
title: "CREATE TEMPORARY TABLE AS (CTTAS)"
-date: 2017-03-15 19:35:02 UTC
+date: 2017-03-27 18:12:49 UTC
parent: "SQL Commands"
---
As of Drill 1.10, you can use the CREATE TEMPORARY TABLE AS (CTTAS) command to store the results of a query in a temporary table. You can reference the temporary table in subsequent queries within the same session, thereby improving query performance. Data written to the temporary table is not permanently stored on the filesystem. Drill automatically drops the temporary table once the session ends or the Drillbit process fails. Therefore, you do not have to manually drop the table.
@@ -24,9 +24,7 @@ As of Drill 1.10, you can use the CREATE TEMPORARY TABLE AS (CTTAS) command to s
###Workspace for Temporary Tables
-By default, Drill creates temporary tables within the default temporary workspace, `dfs.tmp`. The default temporary workspace must be writable, file-based, and point to a location that
-
-already exists, otherwise temporary tables creation will fail. You cannot create a temporary table outside of the default temporary workspace.
+By default, Drill creates temporary tables within the default temporary workspace, `dfs.tmp`. The default temporary workspace must be writable, file-based, and point to a location that already exists, otherwise temporary table creation fails. You cannot create a temporary table outside of the default temporary workspace.
Example dfs.tmp workspace in the dfs storage plugin:
@@ -87,9 +85,11 @@ When you mention a table name in a SELECT statement, any temporary table with th
For example, when you issue a SELECT statement on a table name that is common among the default temporary tables workspace and the current workspace, the temporary table is returned:
- USE dfs.json;
+ USE dfs.json;
- SELECT * FROM donuts; //returns table from dfs.tmp SELECT* FROM dfs.json.donuts; //returns table from dfs.json
+ SELECT * FROM donuts; //returns table from dfs.tmp
+
+ SELECT* FROM dfs.json.donuts; //returns table from dfs.json
###Drop a Temporary Table
http://git-wip-us.apache.org/repos/asf/drill/blob/479339d7/blog/_posts/2017-03-15-drill-1.10-released.md
----------------------------------------------------------------------
diff --git a/blog/_posts/2017-03-15-drill-1.10-released.md b/blog/_posts/2017-03-15-drill-1.10-released.md
index a9ea659..68c8585 100644
--- a/blog/_posts/2017-03-15-drill-1.10-released.md
+++ b/blog/_posts/2017-03-15-drill-1.10-released.md
@@ -20,7 +20,7 @@ An optional `tries=<value>` parameter included in the JDBC connection string ind
The Web Console displays additional query profile statistics and the Drill version running on each Drill node in the cluster. See [Identifying Multiple Drill Versions in a Cluster]({{site.baseurl}}/docs/identifying-multiple-drill-versions-in-a-cluster).
## Implicit Interpretation of INT96
-Drill implicitly interprets the INT96 timestamp data type in Parquet files when the new `store.parquet.int96_as_timestamp` option is enabled. See [About INT96 Support]({{site.baseurl}}/docs/parquet-format/#about-int96-support).
+Drill implicitly interprets the INT96 timestamp data type in Parquet files when the new `store.parquet.reader.int96_as_timestamp` option is enabled. See [About INT96 Support]({{site.baseurl}}/docs/parquet-format/#about-int96-support).
## Kerberos Authentication
Drill supports Kerberos authentication between the client and drillbit. See [Configuring Kerberos Authentication]({{site.baseurl}}/docs/configuring-kerberos-authentication/) in the [Securing Drill]({{site.baseurl}}/docs/securing-drill/) section.