drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject [1/2] drill git commit: typo
Date Wed, 07 Oct 2015 23:53:56 GMT
Repository: drill
Updated Branches:
  refs/heads/gh-pages 0e1d52a27 -> 9ac37a861


typo

ODBC Diable Asynch update

typo

1.2 updates

Krystal's changes

Aman's changes


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

Branch: refs/heads/gh-pages
Commit: 90678c85caa0f8961094485902d8554c96f212e0
Parents: 0e1d52a
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Wed Oct 7 13:51:54 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Wed Oct 7 16:17:20 2015 -0700

----------------------------------------------------------------------
 _docs/getting-started/010-drill-introduction.md |   2 +-
 _docs/img/explorer-connect.png                  | Bin 31369 -> 29945 bytes
 _docs/img/explorer-schemas.png                  | Bin 15580 -> 14332 bytes
 _docs/img/odbc-configure2.png                   | Bin 48218 -> 56060 bytes
 _docs/img/odbc-configure3.png                   | Bin 49108 -> 57224 bytes
 _docs/img/odbc-define-view.png                  | Bin 88744 -> 88806 bytes
 _docs/img/odbc-explorer-win.png                 | Bin 25610 -> 24127 bytes
 .../010-odbc-configuration-reference.md         |  29 ++++++++++---------
 .../020-configuring-odbc-on-linux.md            |  13 +++++----
 .../025-configuring-odbc-on-mac-os-x.md         |  15 ++++++----
 .../030-configuring-odbc-on-windows.md          |   7 ++++-
 .../040-testing-the-odbc-connection.md          |   6 ++--
 .../020-installing-the-driver-on-mac-os-x.md    |   2 +-
 .../040-installing-the-tdc-file-on-windows.md   |   2 +-
 .../030-browsing-data-and-creating-views.md     |   2 +-
 .../025-optimizing-parquet-reading.md           |  11 ++++---
 16 files changed, 50 insertions(+), 39 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/getting-started/010-drill-introduction.md
----------------------------------------------------------------------
diff --git a/_docs/getting-started/010-drill-introduction.md b/_docs/getting-started/010-drill-introduction.md
index ae5c9db..062af4c 100644
--- a/_docs/getting-started/010-drill-introduction.md
+++ b/_docs/getting-started/010-drill-introduction.md
@@ -15,7 +15,7 @@ This release of Drill fixes [many issues]() and introduces a number of enhanceme
 
 * A number of new [SQL window functions]({{site.baseurl}}/docs/sql-window-functions)  
   * [NTILE]({{site.baseurl}}/docs/ranking-window-functions/#ntile)  
-  * [LEAD and LEAD]({{site.baseurl}}/docs/value-window-functions/#lag-lead)  
+  * [LAG and LEAD]({{site.baseurl}}/docs/value-window-functions/#lag-lead)  
   * [FIRST_VALUE and LAST_VALUE]({{site.baseurl}}/docs/value-window-functions/#first_value-last_value)
 
 * [Security]({{site.baseurl}}/docs/configuring-web-console-and-rest-api-security/) for Web
Console and REST API operations  
 * Performance improvements for [querying HBase]({{site.baseurl}}/docs/querying-hbase/#querying-big-endian-encoded-data),
which includes leveraging [ordered byte encoding]({{site.baseurl}}/docs/querying-hbase/#leveraging-hbase-ordered-byte-encoding)
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/explorer-connect.png
----------------------------------------------------------------------
diff --git a/_docs/img/explorer-connect.png b/_docs/img/explorer-connect.png
index b89c8f8..752bce9 100644
Binary files a/_docs/img/explorer-connect.png and b/_docs/img/explorer-connect.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/explorer-schemas.png
----------------------------------------------------------------------
diff --git a/_docs/img/explorer-schemas.png b/_docs/img/explorer-schemas.png
index 4f8ad9f..3a9a53a 100644
Binary files a/_docs/img/explorer-schemas.png and b/_docs/img/explorer-schemas.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/odbc-configure2.png
----------------------------------------------------------------------
diff --git a/_docs/img/odbc-configure2.png b/_docs/img/odbc-configure2.png
index 21db003..af79337 100755
Binary files a/_docs/img/odbc-configure2.png and b/_docs/img/odbc-configure2.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/odbc-configure3.png
----------------------------------------------------------------------
diff --git a/_docs/img/odbc-configure3.png b/_docs/img/odbc-configure3.png
index e04707b..9d6e9e0 100755
Binary files a/_docs/img/odbc-configure3.png and b/_docs/img/odbc-configure3.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/odbc-define-view.png
----------------------------------------------------------------------
diff --git a/_docs/img/odbc-define-view.png b/_docs/img/odbc-define-view.png
index 70b4af8..07ed985 100644
Binary files a/_docs/img/odbc-define-view.png and b/_docs/img/odbc-define-view.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/img/odbc-explorer-win.png
----------------------------------------------------------------------
diff --git a/_docs/img/odbc-explorer-win.png b/_docs/img/odbc-explorer-win.png
index 5d37cc9..04bda8a 100644
Binary files a/_docs/img/odbc-explorer-win.png and b/_docs/img/odbc-explorer-win.png differ

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/configuring-odbc/010-odbc-configuration-reference.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/configuring-odbc/010-odbc-configuration-reference.md
b/_docs/odbc-jdbc-interfaces/configuring-odbc/010-odbc-configuration-reference.md
index 797644e..891d287 100644
--- a/_docs/odbc-jdbc-interfaces/configuring-odbc/010-odbc-configuration-reference.md
+++ b/_docs/odbc-jdbc-interfaces/configuring-odbc/010-odbc-configuration-reference.md
@@ -13,20 +13,21 @@ Drill ODBC Driver. You can use these options in a connection string or
in the
 
 The following table provides a list of the configuration options and a brief description.
Subsequent sections describe options in more detail:
 
-| Property           | Valid Values                              | Brief Description    
                                                                                         
                                                        |
-|--------------------|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Catalog            | DRILL                                     | The name of the synthetic
catalog under which all of the schemas/databases are organized.                          
                                                    |
-| ConnectionType     | Direct or ZooKeeper                       | Direct connects to a Drill
server using Host and Port properties. ZooKeeper connects to a ZooKeeper cluster using ZKQuorum
and ZKClusterID properties.                  |
-| Driver             | MapR Drill ODBC Driver                    | The name of the installed
driver.                                                                                  
                                                    |
-| Host               | \<host name\>                             | If the ConnectionType
property is set to Direct, set the host name of the Drill server using the Host property.
                                                        |
-| Port               | 31010                                     | If the ConnectionType
property is set to Direct, set the e TCP port on which the Drill server is listening.    
                                                        |
-| Schema             | \<schema name\>                           | The name of the
database schema or storage plugin name to use when the query does not explicitly specify the
schema or storage plugin.                                  |
-| ZKClusterID        | drillbits1                                | If the ConnectionType
property is set to ZooKeeper, then set ZKClusterID to the name of the Drillbit cluster to
use.                                                    |
-| ZKQuorum           | \<IP address\>,\<IP address\> . . .       | If the ConnectionType
property is set to ZooKeeper, then use ZKQuorum to indicate the server(s) in your ZooKeeper
cluster. Separate multiple servers using a comma (,). |
-| AuthenticationType | No Authentication or Basic Authentication | Basic Authentication enables
[impersonation]({{site.baseurl}}/docs/configuring-user-impersonation/).                  
                                                 |
-| UID                | \<user name\>                             | If AuthenticationType
is Basic Authentication, set the UID to a user name.                                     
                                                        |
-| PWD                | \<password\>                              | If AuthenticationType
is Basic Authentication, set the PWD to a password.                                      
                                                        |
-| AdvancedProperties | {\<property\>;\<property\>; . . .}        | Separate advanced
properties using a semi-colon (;) and then surround all advanced properties in a connection
string using braces { and }.                              |
+| Property           | Valid Values                              | Brief Description    
                                                                                         
                                                                |
+|--------------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Catalog            | DRILL                                     | The name of the synthetic
catalog under which all of the schemas/databases are organized.                          
                                                            |
+| ConnectionType     | Direct or ZooKeeper                       | Direct connects to a Drill
server using Host and Port properties. ZooKeeper connects to a ZooKeeper cluster using ZKQuorum
and ZKClusterID properties.                          |
+| Driver             | MapR Drill ODBC Driver                    | The name of the installed
driver.                                                                                  
                                                            |
+| Host               | \<host name\>                             | If the ConnectionType
property is set to Direct, set the host name of the Drill server using the Host property.
                                                                |
+| Port               | 31010                                     | If the ConnectionType
property is set to Direct, set the e TCP port on which the Drill server is listening.    
                                                                |
+| Schema             | \<schema name\>                           | The name of the
database schema or storage plugin name to use when the query does not explicitly specify the
schema or storage plugin.                                          |
+| ZKClusterID        | drillbits1                                | If the ConnectionType
property is set to ZooKeeper, then set ZKClusterID to the name of the Drillbit cluster to
use.                                                            |
+| ZKQuorum           | \<IP address\>,\<IP address\> . . .       | If the ConnectionType
property is set to ZooKeeper, then use ZKQuorum to indicate the server(s) in your ZooKeeper
cluster. Separate multiple servers using a comma (,).         |
+| AuthenticationType | No Authentication or Basic Authentication | Basic Authentication enables
[impersonation]({{site.baseurl}}/docs/configuring-user-impersonation/).                  
                                                         |
+| UID                | \<user name\>                             | If AuthenticationType
is Basic Authentication, set the UID to a user name.                                     
                                                                |
+| PWD                | \<password\>                              | If AuthenticationType
is Basic Authentication, set the PWD to a password.                                      
                                                                |
+| AdvancedProperties | {\<property\>;\<property\>; . . .}        | Separate advanced
properties using a semi-colon (;) and then surround all advanced properties in a connection
string using braces { and }.                                      |
+| DisableAsync       | 0 or 1                                    | Disables asynchronous
ODBC connection and enables a synchronous connection. A change in state occurs during driver
initialization and is propagated to all driver DSNs.         |
 
 ### Catalog
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/configuring-odbc/020-configuring-odbc-on-linux.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/configuring-odbc/020-configuring-odbc-on-linux.md
b/_docs/odbc-jdbc-interfaces/configuring-odbc/020-configuring-odbc-on-linux.md
index e89103a..ba1e88b 100644
--- a/_docs/odbc-jdbc-interfaces/configuring-odbc/020-configuring-odbc-on-linux.md
+++ b/_docs/odbc-jdbc-interfaces/configuring-odbc/020-configuring-odbc-on-linux.md
@@ -158,6 +158,7 @@ file. This configures the driver to work with your ODBC driver manager.
The foll
 
     . . .
     [Driver]
+    DisableAsync=0
     DriverManagerEncoding=UTF-32
     ErrorMessagesPath=/opt/mapr/drillodbc/ErrorMessages
     LogLevel=0
@@ -176,15 +177,17 @@ file. This configures the driver to work with your ODBC driver manager.
The foll
 
 To configure the MapR Drill ODBC Driver in the `mapr.drillodbc.ini` configuration file, complete
the following steps:
 
-  1. Open the `mapr.drillodbc.ini` configuration file in a text editor.
-  2. Edit the DriverManagerEncoding setting if necessary. The value is typically UTF-16 or
UTF-32, but depends on the driver manager used. iODBC uses UTF-32 and unixODBC uses UTF-16.
Review your ODBC Driver Manager documentation for the correct setting.
-  3. Edit the `ODBCInstLib` setting. The value is the name of the `ODBCInst` shared library
for the ODBC driver manager that you use. The configuration file defaults to the shared library
for `iODBC`. In Linux, the shared library name for iODBC is `libiodbcinst.so`. 
+  1. Open the `mapr.drillodbc.ini` configuration file in a text editor.  
+  2. Edit the DisableAsync setting if you want to enable a synchronous ODBC connection for
performance reasons. Change the default 0 to 1 to disable the asynchronous and enable the
synchronous connection.  
+     A change in state occurs during driver initialization and is propagated to all driver
DSNs.  
+  3. Edit the DriverManagerEncoding setting if necessary. The value is typically UTF-16 or
UTF-32, but depends on the driver manager used. iODBC uses UTF-32 and unixODBC uses UTF-16.
Review your ODBC Driver Manager documentation for the correct setting.  
+  4. Edit the `ODBCInstLib` setting. The value is the name of the `ODBCInst` shared library
for the ODBC driver manager that you use. The configuration file defaults to the shared library
for `iODBC`. In Linux, the shared library name for iODBC is `libiodbcinst.so`.  
      
      Specify an absolute or relative filename for the library. If you use
 the relative file name, include the path to the library in the library path
 environment variable. The library path environment variable is named
-`LD_LIBRARY_PATH`. 
-  4. Save the `mapr.drillodbc.ini` configuration file.
+`LD_LIBRARY_PATH`.  
+  5. Save the `mapr.drillodbc.ini` configuration file.
 
 ### Next Step
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/configuring-odbc/025-configuring-odbc-on-mac-os-x.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/configuring-odbc/025-configuring-odbc-on-mac-os-x.md
b/_docs/odbc-jdbc-interfaces/configuring-odbc/025-configuring-odbc-on-mac-os-x.md
index 6c00db3..68abbe0 100644
--- a/_docs/odbc-jdbc-interfaces/configuring-odbc/025-configuring-odbc-on-mac-os-x.md
+++ b/_docs/odbc-jdbc-interfaces/configuring-odbc/025-configuring-odbc-on-mac-os-x.md
@@ -14,7 +14,7 @@ steps:
 ## Sample Configuration Files
 
 Before you connect to Drill through an ODBC client tool
-on Mac OS X, copy the following configuration files in `/opt/mapr/drillobdc/Setup` to your
home directory unless the files already exist in your home directory:
+on Mac OS X, copy the following configuration files in `/opt/mapr/drillodbc/Setup` to your
home directory unless the files already exist in your home directory:
 
 * `mapr.drillodbc.ini`
 * `odbc.ini`
@@ -156,6 +156,7 @@ file. This configures the driver to work with your ODBC driver manager.
The foll
 
     [Driver]
     ## - Note that this default DriverManagerEncoding of UTF-32 is for iODBC.
+    DisableAsync=0
     DriverManagerEncoding=UTF-32
     ErrorMessagesPath=/opt/mapr/drillodbc/ErrorMessages
 
@@ -170,15 +171,17 @@ file. This configures the driver to work with your ODBC driver manager.
The foll
 
 To configure the MapR Drill ODBC Driver in the `mapr.drillodbc.ini` configuration file, complete
the following steps:
 
-  1. Open the `mapr.drillodbc.ini` configuration file in a text editor.
-  2. Edit the DriverManagerEncoding setting if necessary. The value is typically UTF-16 or
UTF-32, but depends on the driver manager used. iODBC uses UTF-32 and unixODBC uses UTF-16.
Review your ODBC Driver Manager documentation for the correct setting.
-  3. Edit the `ODBCInstLib` setting. The value is the name of the `ODBCInst` shared library
for the ODBC driver manager that you use. The configuration file defaults to the shared library
for `iODBC`. The shared library name for `iODBC` is `libiodbcinst.dylib`.
+  1. Open the `mapr.drillodbc.ini` configuration file in a text editor.  
+  2. Edit the DisableAsync setting if you want to enable a synchronous ODBC connection for
performance reasons. Change the default 0 to 1 to disable the asynchronous and enable the
synchronous connection.  
+     A change in state occurs during driver initialization and is propagated to all driver
DSNs.  
+  3. Edit the DriverManagerEncoding setting if necessary. The value is typically UTF-16 or
UTF-32, but depends on the driver manager used. iODBC uses UTF-32 and unixODBC uses UTF-16.
Review your ODBC Driver Manager documentation for the correct setting.  
+  4. Edit the `ODBCInstLib` setting. The value is the name of the `ODBCInst` shared library
for the ODBC driver manager that you use. The configuration file defaults to the shared library
for `iODBC`. The shared library name for `iODBC` is `libiodbcinst.dylib`.  
       
      Specify an absolute or relative filename for the library. If you use
 the relative file name, include the path to the library in the library path
 environment variable. The library path environment variable is
-named `DYLD_LIBRARY_PATH`.
-  4. Save the `mapr.drillodbc.ini` configuration file.
+named `DYLD_LIBRARY_PATH`.  
+  5. Save the `mapr.drillodbc.ini` configuration file.
 
 ### Next Step
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/configuring-odbc/030-configuring-odbc-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/configuring-odbc/030-configuring-odbc-on-windows.md
b/_docs/odbc-jdbc-interfaces/configuring-odbc/030-configuring-odbc-on-windows.md
index 71bc2d5..79475e2 100644
--- a/_docs/odbc-jdbc-interfaces/configuring-odbc/030-configuring-odbc-on-windows.md
+++ b/_docs/odbc-jdbc-interfaces/configuring-odbc/030-configuring-odbc-on-windows.md
@@ -50,7 +50,12 @@ If you select ZooKeeper Quorum, provide values for the following properties:
  Check the `drill-override.conf` file for the cluster name.
 ![]({{ site.baseurl }}/docs/img/odbc-configure3.png)
 
-[Advanced Properties]({{site.baseurl}}/docs/odbc-configuration-reference/), [logging options]({{site.baseurl}}/docs/odbc-configuration-reference/#logging-options),
and [Drill Explorer]({{site.baseurl}}/docs/drill-explorer-introduction/) sections describe
the options at the bottom of this dialog.
+The [Advanced Properties]({{site.baseurl}}/docs/odbc-configuration-reference/) section describes
the advanced properties.
+
+Select the Disable Async option to disable the asynchronous ODBC connection and enable a
synchronous ODBC connection for performance reasons. By default the ODBC connection is asynchronous
(Disable Asynch is not checked). A change in state occurs during driver initialization and
is propagated to all driver DSNs.
+
+
+[Logging Options]({{site.baseurl}}/docs/odbc-configuration-reference/#logging-options) and
[Drill Explorer]({{site.baseurl}}/docs/drill-explorer-introduction/) sections describe the
options at the bottom of this dialog.
 
 ### Next Step
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/configuring-odbc/040-testing-the-odbc-connection.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/configuring-odbc/040-testing-the-odbc-connection.md
b/_docs/odbc-jdbc-interfaces/configuring-odbc/040-testing-the-odbc-connection.md
index 88bf8e3..e88871f 100644
--- a/_docs/odbc-jdbc-interfaces/configuring-odbc/040-testing-the-odbc-connection.md
+++ b/_docs/odbc-jdbc-interfaces/configuring-odbc/040-testing-the-odbc-connection.md
@@ -25,8 +25,8 @@ To test the ODBC connection on a Linux cluster, follow these steps:
 
 1. [Start Drill]({{site.baseurl}}/docs/starting-drill-on-linux-and-mac-os-x/). For example,
to start Drill in local mode on a linux cluster:  
 
-        [root@centos23 drill-1.0.0]# bin/drill-localhost
-        apache drill 1.0.0 
+        [root@centos23 drill-1.2.0]# bin/drill-localhost
+        apache drill 1.2.0 
         "the only truly happy people are children, the creative minority and drill users"
 
 2. In the `samples` directory of the driver manager installation, run `iodbctest` or `iodbctestw`.
 
@@ -58,7 +58,7 @@ To test the ODBC connection on a Linux cluster, follow these steps:
         DSN=<DSN Name>;ConnectionType=ZooKeeper;ZKQuorum=<Server1:Port1>,<Server2:Port2>;ZKClusterID=<Cluster
Name>`
 
      The output of a successful test is:  
-     `Driver: 1.0.0.1001 (MapR Drill ODBC Driver)  
+     `Driver: 1.2.0.1001 (MapR Drill ODBC Driver)  
      SQL> `  
      After the `SQL>` prompt appears, type `quit;`, and go to the Drill shell to run commands.
Do not attempt to run SQL commands from this prompt.
 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/020-installing-the-driver-on-mac-os-x.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/020-installing-the-driver-on-mac-os-x.md
b/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/020-installing-the-driver-on-mac-os-x.md
index 4a7bd3b..2d8d164 100644
--- a/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/020-installing-the-driver-on-mac-os-x.md
+++ b/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/020-installing-the-driver-on-mac-os-x.md
@@ -56,7 +56,7 @@ To check the version of the driver you installed, use the following command
on t
 
     $ pkgutil --info mapr.drillodbc
     package-id: mapr.drillodbc
-    version: 1.0.0
+    version: 1.2.0
     volume: /
     location: 
     install-time: 1433465518

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/040-installing-the-tdc-file-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/040-installing-the-tdc-file-on-windows.md
b/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/040-installing-the-tdc-file-on-windows.md
index d922e24..1979ea5 100644
--- a/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/040-installing-the-tdc-file-on-windows.md
+++ b/_docs/odbc-jdbc-interfaces/installing-the-odbc-driver/040-installing-the-tdc-file-on-windows.md
@@ -7,7 +7,7 @@ The MapR Drill ODBC driver installer automatically installs the TDC file if
the
 **To install the MapRDrillODBC.TDC file manually:**
 
 1. Click **Start**, and locate the Install Tableau TDC File app that the MapR Drill ODBC
Driver installer installed.   
-   For example, on Windows 8.1 in Apps, the Install Tableau TDC File appears under MaprDrill
ODBC Driver 1.0:
+   For example, on Windows 8.1 in Apps, the Install Tableau TDC File appears under MaprDrill
ODBC Driver:
    ![]({{ site.baseurl }}/docs/img/odbc-mapr-drill-apps.png)
 
 2. Click **Install Tableau TDC File**. 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/odbc-jdbc-interfaces/using-drill-explorer/030-browsing-data-and-creating-views.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-drill-explorer/030-browsing-data-and-creating-views.md
b/_docs/odbc-jdbc-interfaces/using-drill-explorer/030-browsing-data-and-creating-views.md
index 66b2983..bd01f76 100644
--- a/_docs/odbc-jdbc-interfaces/using-drill-explorer/030-browsing-data-and-creating-views.md
+++ b/_docs/odbc-jdbc-interfaces/using-drill-explorer/030-browsing-data-and-creating-views.md
@@ -34,7 +34,7 @@ The following example defines and saves a view of a few columns of `nation.parqu
 3. In the **Schemas** section on the **Browse** tab, navigate to the `/sample-data/nation.parquet`
in the `dfs.default` schema. 
 4. On the **SQL** tab, in the **View Definition SQL** field, enter a query, as described
in the [Specifying Column Names](). For example, modify the SELECT statement as follows:
 
-        SELECT N_NAME, N_REGIONKEY FROM `dfs.default`.`./Users/drilluser/drill/apache-drill-1.0.0/sample-data/nation.parquet`
WHERE N_REGIONKEY IN (2, 4)
+        SELECT N_NAME, N_REGIONKEY FROM `dfs.default`.`./Users/drilluser/drill/sample-data/nation.parquet`
WHERE N_REGIONKEY IN (2, 4)
    Do not put a semicolon at the end of the SQL statement.  
 5. Click **Preview**.
    ![nation parquet]({{ site.baseurl }}/docs/img/odbc-define-view.png) 

http://git-wip-us.apache.org/repos/asf/drill/blob/90678c85/_docs/performance-tuning/025-optimizing-parquet-reading.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/025-optimizing-parquet-reading.md b/_docs/performance-tuning/025-optimizing-parquet-reading.md
index 471af37..de04d2e 100644
--- a/_docs/performance-tuning/025-optimizing-parquet-reading.md
+++ b/_docs/performance-tuning/025-optimizing-parquet-reading.md
@@ -3,13 +3,12 @@ title: "Optimizing Parquet Reading"
 parent: "Performance Tuning"
 ---
 
-Parquet metadata caching is an optional feature in Drill 1.2 and later. When you use this
feature, Drill generates a metadata cache file. Drill stores the metadata cache file  in a
directory you specify and its subdirectories. When you run a query on this directory or a
subdirectory, Drill reads the metadata cache file instead of the actual files that contain
the metadata during the query-planning phase. You can realize performance improvements during
the query-planning phase when Drill reads just one metadata file instead of reading multiple
files to fetch the metadata.
-
-The Parquet metadata caching feature enables Drill to speed up the cost of query planning.
The actual query runtime will not be improved if the planning cost is not a bottleneck.
+Parquet metadata caching is an optional feature in Drill 1.2 and later. When you use this
feature, Drill generates a metadata cache file. Drill stores the metadata cache file  in a
directory you specify and its subdirectories. When you run a query on this directory or a
subdirectory, Drill reads a single metadata cache file instead of retrieving metadata from
multiple Parquet files during the query-planning phase.
 
 ## When to Use Parquet Metadata Caching
 
-Use Parquet metadata caching to optimize reads only when the planning phase of a query takes
longer than the execution phase. Before using this feature, run your query and compare the
time for executing the logical (planning) and physical (execution) operations to see if using
this feature makes sense. The logical/planning operations must take longer than the physical/execution
operations; otherwise, do not create Parquet metadata because Drill cannot optimize reads
under these conditions.
+The scenarios in which metadata caching is useful is when the planning time is a significant
percentage of the total elapsed time of the query. If the query execution time is the dominant
factor then metadata caching will have very little impact. Before using this feature, run
an EXPLAIN plan on your query and compare its time to the total time of query execution. Use
these timings to determine whether metadata caching will be useful.
+
 
 ## How to Trigger Generation of the Parquet Metadata Cache File
 
@@ -19,7 +18,7 @@ The following command generates the Parquet metadata cache file in the `<path
to
 
 You need to run this command on a directory, nested or flat, only once during the session.
Only the first query gathers the metadata unless the Parquet data changes, for example, you
delete some data. If you did not make changes to the Parquet data, subsequent queries encounter
the up-to-date Parquet metadata files. There is no need for Drill to regenerate the metadata.
If there are changes, the metadata needs updating, so Drill regenerates the Parquet metadata
when you issue the next query.
 
-The elapsed time of any queries that trigger regeneration of data can be greater than that
of other queries.
+The elapsed time of the first query that triggers regeneration of metadata can be greater
than that of subsequent queries that use that metadata.
 
 ## Example of Generating Parquet Metadata
 
@@ -35,6 +34,6 @@ The elapsed time of any queries that trigger regeneration of data can be
greater
 
 ## How Drill Generates and Uses Parquet Metadata
 
-After running the REFRESH TABLE METADATA command, Drill traverses directories in the case
of nested directories to find the Parquet files. From the footers of the files, Drill gathers
metadata, such as row counts and node affinity based on HDFS block locations. For each directory
level, Drill saves a summary of the information from the footers in a single Parquet metadata
cache file. The summary at each level covers that particular level and all lower levels; consequently,
after generating metadata, you can query nested directories from any level. For example, you
can query a subdirectory of Parquet files because Drill stores a Parquet metadata cache file
at each level.
+After running the REFRESH TABLE METADATA command, Drill traverses directories in the case
of nested directories to find the Parquet files. From the footers of the files, Drill gathers
metadata, such as row counts and node affinity based on HDFS block locations. For each directory
level, Drill saves a summary of the information from the footers in a single Parquet metadata
cache file. The summary at each level covers that particular level and all child levels; consequently,
after generating metadata, you can query nested directories from any level. In order to leverage
the metadata cache file for a table t, the file must exist at the root directory of that table.
For example, you can query a subdirectory of Parquet files because Drill stores a Parquet
metadata cache file at each level.
 
 At planning time, Drill reads only the metadata file. Parquet metadata caching has no effect
on execution time. At execution time, Drill reads the actual files.
\ No newline at end of file


Mime
View raw message