drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject [4/5] drill git commit: INTERVAL fix
Date Tue, 11 Aug 2015 21:51:31 GMT
INTERVAL fix

fix hexadecimal section formatting

hide 1.2 features


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/d20ebcd1
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/d20ebcd1
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/d20ebcd1

Branch: refs/heads/gh-pages
Commit: d20ebcd13c198bef94774946856cf97cacb0e1dc
Parents: 93ccbc8
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Tue Aug 11 14:20:59 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Tue Aug 11 14:23:29 2015 -0700

----------------------------------------------------------------------
 .../040-parquet-format.md                       |  4 +-
 .../020-querying-parquet-files.md               |  4 +-
 .../data-types/010-supported-data-types.md      | 57 ++++++++++----------
 .../sql-functions/020-data-type-conversion.md   |  8 +--
 4 files changed, 36 insertions(+), 37 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/d20ebcd1/_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 ff700fb..867c4f4 100644
--- a/_docs/data-sources-and-file-formats/040-parquet-format.md
+++ b/_docs/data-sources-and-file-formats/040-parquet-format.md
@@ -20,7 +20,7 @@ Apache Drill includes the following support for Parquet:
 ## Reading Parquet Files
 When a read of Parquet data occurs, Drill loads only the necessary columns of data, which
reduces I/O. Reading only a small piece of the Parquet data from a data file or table, Drill
can examine and analyze all values for a column across multiple files. You can create a Drill
table from one format and store the data in another format, including Parquet.
 
-## Caching Metadata
+<!-- ## Caching Metadata
 
 For performant querying of a large number of files, Drill can take advantage of metadata,
such as the Hive metadata store, and includes the capability of generating a metadata cache
for performant querying of thousands of Parquet files. The metadata cache is not a central
caching system, but simply one or more files of metadata. Drill generates and saves a cache
of metadata in each directory in nested directories. You trigger the generation of metadata
caches by running the REFRESH TABLE METADATA command, as described in [Querying Parquet Files]({{site.baseurl}}/docs/querying-parquet-files/).
 
@@ -33,7 +33,7 @@ After generating the metadata cache, Drill performs the following tasks
during t
 * Summarizes the information from the footers in a single metadata cache file.  
 * Stores the metadata cache file at each level that covers that particular level and all
lower levels.
 
-At execution time, Drill reads the actual files. At planning time, Drill reads only the metadata
file.
+At execution time, Drill reads the actual files. At planning time, Drill reads only the metadata
file. -->
 
 ## Writing Parquet Files
 CREATE TABLE AS (CTAS) can use any data source provided by the storage plugin. To write Parquet
data using the CTAS command, set the session store.format option as shown in the next section.
Alternatively, configure the storage plugin to point to the directory containing the Parquet
files.

http://git-wip-us.apache.org/repos/asf/drill/blob/d20ebcd1/_docs/query-data/query-a-file-system/020-querying-parquet-files.md
----------------------------------------------------------------------
diff --git a/_docs/query-data/query-a-file-system/020-querying-parquet-files.md b/_docs/query-data/query-a-file-system/020-querying-parquet-files.md
index 30e55f7..b166386 100644
--- a/_docs/query-data/query-a-file-system/020-querying-parquet-files.md
+++ b/_docs/query-data/query-a-file-system/020-querying-parquet-files.md
@@ -3,7 +3,7 @@ title: "Querying Parquet Files"
 parent: "Querying a File System"
 ---
 
-Drill extends SQL for performant querying of a large number, thousands or more, of Parquet
files. By including the following command in a query, you trigger the generation of metadata
files in the directory of Parquet files and its subdirectories:
+<!-- Drill extends SQL for performant querying of a large number, thousands or more, of
Parquet files. By including the following command in a query, you trigger the generation of
metadata files in the directory of Parquet files and its subdirectories:
 
     REFRESH TABLE METADATA <path to table>
 
@@ -15,7 +15,7 @@ You can query nested directories from any level. For example, you can query
a su
 
 TBD (fill in when the feature is ready)
 
-## Sample Parquet Files
+## Sample Parquet Files -->
 The Drill installation includes a `sample-data` directory with Parquet files
 that you can query. Use SQL syntax to query the `region.parquet` and
 `nation.parquet` files in the `sample-data` directory.

http://git-wip-us.apache.org/repos/asf/drill/blob/d20ebcd1/_docs/sql-reference/data-types/010-supported-data-types.md
----------------------------------------------------------------------
diff --git a/_docs/sql-reference/data-types/010-supported-data-types.md b/_docs/sql-reference/data-types/010-supported-data-types.md
index 910ccbc..d21f133 100644
--- a/_docs/sql-reference/data-types/010-supported-data-types.md
+++ b/_docs/sql-reference/data-types/010-supported-data-types.md
@@ -2,7 +2,7 @@
 title: "Supported Data Types"
 parent: "Data Types"
 ---
-Drill reads from and writes to data sources having a wide variety of types. Drill uses data
types at the RPC level that are not supported for query input, often implicitly casting data.
Drill supports the following SQL data types for query input:
+Drill reads from and writes to data sources having a wide variety of types. Drill uses data
types at the RPC level that are not supported for query input, such as INTERVALDAY and INTERVALYEAR
types, often implicitly casting data. Drill supports the following SQL data types for query
input:
 
 | SQL Data Type                                     | Description                       
                                                                                  | Example
                                                                       |
 |---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------|
@@ -14,8 +14,7 @@ Drill reads from and writes to data sources having a wide variety of types.
Dril
 | FLOAT                                             | 4-byte floating point number      
                                                                                  | 0.456
                                                                         |
 | DOUBLE, DOUBLE PRECISION                          | 8-byte floating point number, precision-scalable
                                                                    | 0.456              
                                                           |
 | INTEGER or INT                                    | 4-byte signed integer in the range
-2,147,483,648 to 2,147,483,647                                                   | 2147483646
                                                                    |
-| INTERVALDAY                                       | A period of time in days, hours, minutes,
and seconds only                                                           | '1 10:20:30.123'
                                                              |
-| INTERVALYEAR                                      | A period of time in years and months
only                                                                            | '1-2' year
to month                                                            |
+| INTERVAL                                          | A period of time in days, hours, minutes,
and seconds only (INTERVALDAY) or in years and months (INTERVALYEAR)       | '1 10:20:30.123'
(INTERVALDAY) or '1-2' year to month (INTERVALYEAR)           |
 | SMALLINT**                                        | 2-byte signed integer in the range
-32,768 to 32,767                                                                 | 32000
                                                                         |
 | TIME                                              | 24-hour based time before or after
January 1, 2001 in hours, minutes, seconds format: HH:mm:ss                       | 22:55:55.23
                                                                   |
 | TIMESTAMP                                         | JDBC timestamp in year, month, date
hour, minute, second, and optional milliseconds format: yyyy-MM-dd HH:mm:ss.SSS  | 2015-12-30
22:55:55.23                                                         |
@@ -99,23 +98,23 @@ The following list includes data types Drill uses in descending order
of precede
 
     SELECT myBigInt FROM mytable WHERE myBigInt = 2.5;
 
-As shown in the table, Drill can cast a NULL value, which has the lowest precedence, to any
other type; you can cast a SMALLINT (not supported in this release) value to INT. Drill might
deviate from these precedence rules for performance reasons. Under certain circumstances,
such as queries involving SUBSTR and CONCAT functions, Drill reverses the order of precedence
and allows a cast to VARCHAR from a type of higher precedence than VARCHAR, such as BIGINT.
+As shown in the table, Drill can cast a NULL value, which has the lowest precedence, to any
other type; you can cast a SMALLINT (not supported in this release) value to INT. Drill might
deviate from these precedence rules for performance reasons. Under certain circumstances,
such as queries involving SUBSTR and CONCAT functions, Drill reverses the order of precedence
and allows a cast to VARCHAR from a type of higher precedence than VARCHAR, such as BIGINT.
The INTERVALDAY and INTERVALYEAR types are internal types.
 
 ### Casting Precedence
 
-| Precedence | Data Type              | Precedence | Data Type     |
-|------------|------------------------|------------|---------------|
-| 1          | INTERVALYEAR (highest) | 11         | INT           |
-| 2          | INTERVALDAY            | 12         | UINT2         |
-| 3          | TIMESTAMP              | 13         | SMALLINT*     |
-| 4          | DATE                   | 14         | UINT1         |
-| 5          | TIME                   | 15         | VAR16CHAR     |
-| 6          | DOUBLE                 | 16         | FIXED16CHAR   |
-| 7          | DECIMAL                | 17         | VARCHAR       |
-| 8          | UINT8                  | 18         | CHAR          |
-| 9          | BIGINT                 | 19         | VARBINARY     |
-| 10         | UINT4                  | 20         | FIXEDBINARY   |
-|            |                        | 21         | NULL (lowest) |
+| Precedence | Data Type              | Precedence | Data Type      |
+|------------|------------------------|------------|----------------|
+| 1          | INTERVALYEAR (highest) | 12         | UINT2          |
+| 2          | INTERVALDAY            | 13         | SMALLINT*      |
+| 3          | TIMESTAMP              | 14         | UINT1          |
+| 4          | DATE                   | 15         | VAR16CHAR      |
+| 5          | TIME                   | 16         | FIXED16CHAR    |
+| 6          | DOUBLE                 | 17         | VARCHAR        |
+| 7          | DECIMAL                | 18         | CHAR           |
+| 8          | UINT8                  | 19         | VARBINARY      |
+| 9          | BIGINT                 | 20         | FIXEDBINARY    |
+| 10         | UINT4                  | 21         | NULL (lowest)  |
+| 11         | INT                    |            |                |
 
 \* Not supported in this release.
 
@@ -169,18 +168,18 @@ If your FIXEDBINARY or VARBINARY data is in a format other than UTF-8,
such as b
 
 ### Date and Time Data Types
 
-| To:          | DATE | TIME | TIMESTAMP | INTERVALDAY | INTERVALYEAR | INTERVALDAY |
-|--------------|------|------|-----------|-------------|--------------|-------------|
-| From:        |      |      |           |             |              |             |
-| CHAR         | Yes  | Yes  | Yes       | Yes         | Yes          | Yes         |
-| FIXEDBINARY* | No   | No   | No        | No          | No           | No          |
-| VARCHAR      | Yes  | Yes  | Yes       | Yes         | Yes          | Yes         |
-| VARBINARY*   | No   | No   | Yes       | No          | No           | No          |
-| DATE         | No   | No   | Yes       | No          | No           | No          |
-| TIME         | No   | Yes  | Yes       | No          | No           | No          |
-| TIMESTAMP    | Yes  | Yes  | Yes       | No          | No           | No          |
-| INTERVALYEAR | Yes  | No   | Yes       | Yes         | No           | Yes         |
-| INTERVALDAY  | Yes  | No   | Yes       | Yes         | Yes          | No          |
+| To:          | DATE | TIME | TIMESTAMP | INTERVALYEAR | INTERVALDAY |
+|--------------|------|------|-----------|--------------|-------------|
+| From:        |      |      |           |              |             |
+| CHAR         | Yes  | Yes  | Yes       | Yes          | Yes         |
+| FIXEDBINARY* | No   | No   | No        | No           | No          |
+| VARCHAR      | Yes  | Yes  | Yes       | Yes          | Yes         |
+| VARBINARY*   | No   | No   | Yes       | No           | No          |
+| DATE         | No   | No   | Yes       | No           | No          |
+| TIME         | No   | Yes  | Yes       | No           | No          |
+| TIMESTAMP    | Yes  | Yes  | Yes       | No           | No          |
+| INTERVALYEAR | Yes  | No   | Yes       | No           | Yes         |
+| INTERVALDAY  | Yes  | No   | Yes       | Yes          | No          |
 
 \* Used to cast binary UTF-8 data coming to/from sources such as MapR-DB/HBase. The CAST
function does not support all representations of FIXEDBINARY and VARBINARY. Only the UTF-8
format is supported. 
 

http://git-wip-us.apache.org/repos/asf/drill/blob/d20ebcd1/_docs/sql-reference/sql-functions/020-data-type-conversion.md
----------------------------------------------------------------------
diff --git a/_docs/sql-reference/sql-functions/020-data-type-conversion.md b/_docs/sql-reference/sql-functions/020-data-type-conversion.md
index 148cacf..47b2413 100644
--- a/_docs/sql-reference/sql-functions/020-data-type-conversion.md
+++ b/_docs/sql-reference/sql-functions/020-data-type-conversion.md
@@ -390,7 +390,7 @@ Converts a VARBINARY type into a hexadecimal-encoded string.
 
 *expression* is a byte array, such as {(byte)0xca, (byte)0xfe, (byte)0xba, (byte)0xbe}
 
-This function returns a hexadecimal string, such as "\xca\xfe\xba\xbe". You can use this
function with CONVERT_TO when you want to test the effects of a conversion.
+This function returns a hexadecimal string, such as `"\xca\xfe\xba\xbe"`. You can use this
function with CONVERT_TO when you want to test the effects of a conversion.
 
 ### STRING_BINARY Examples
 
@@ -439,7 +439,7 @@ Converts a hexadecimal-encoded string into a VARBINARY type.
 
     BINARY_STRING(expression)
 
-*expression* is a hexadecimal string, such as "\xca\xfe\xba\xbe".
+*expression* is a hexadecimal string, such as `"\xca\xfe\xba\xbe"`.
 
 This function returns a byte array, such as {(byte)0xca, (byte)0xfe, (byte)0xba, (byte)0xbe}.
You can use this function with CONVERT_FROM for readable results.
 
@@ -453,11 +453,11 @@ Converts a VARBINARY type into a hexadecimal-encoded string.
 
 *expression* is a byte array, such as {(byte)0xca, (byte)0xfe, (byte)0xba, (byte)0xbe}.
 
-This function returns a hexadecimal-encoded string, such as "\xca\xfe\xba\xbe". You can use
this function with CONVERT_TO for readable results.
+This function returns a hexadecimal-encoded string, such as `"\xca\xfe\xba\xbe"`. You can
use this function with CONVERT_TO for readable results.
 
 ### BINARY_STRING Examples
 
-Decode the hexadecimal string 000000C8 expressed in four octets \x00\x00\x00\xC8 into its
big endian four-byte integer equivalent. 
+Decode the hexadecimal string 000000C8 expressed in four octets `\x00\x00\x00\xC8` into its
big endian four-byte integer equivalent. 
 
 ```
 SELECT CONVERT_FROM(BINARY_STRING('\x00\x00\x00\xC8'), 'INT_BE') AS cnvrt


Mime
View raw message