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 2015/06/09 01:06:57 UTC

[08/15] drill git commit: reorg and partial update odbc

http://git-wip-us.apache.org/repos/asf/drill/blob/8f1c9a42/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/010-installing-the-driver-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/010-installing-the-driver-on-windows.md b/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/010-installing-the-driver-on-windows.md
deleted file mode 100755
index 6c65f91..0000000
--- a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/010-installing-the-driver-on-windows.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: "Installing the Driver on Windows"
-parent: "Using ODBC on Windows"
----
-The MapR Drill ODBC Driver installer is available for 32-bit and 64-bit
-applications on Windows. Both versions of the driver can be installed on a 64-bit
-machine.
-
-##  System Requirements
-
-Each computer where you install the driver must meet the following system
-requirements:
-
-  * One of the following operating systems (32- and 64-bit editions are supported):
-    * Windows® 8 and 8.1
-    * Windows® 7 Professional
-    * Windows® Server 2012, 2012 R2
-    * Windows® Server 2008, 2013 R2
-  * .NET Framework 4.5.2 is required to run the Drill Explorer application.
-  * 60 MB of available disk space
-  * The client must be able to resolve the actual hostname of the Drill node(s) with the IP(s). Verify that a DNS entry was created on the client machine for the Drill node(s). If not, create the following entry for the Drill node(s) in the `%WINDIR%\system32\drivers\etc\hosts` file:
-    
-    `<drill-machine-IP> <drill-machine-hostname>`  
-    Example: `127.0.1.1 apachedemo`
-
-To install the driver, you need Administrator privileges on the computer.
-
-## Installing the Driver
-
-  1. Download the installer that corresponds to the bitness of the client application from which you want to create an ODBC connection:
-     * [MapR Drill ODBC Driver (32-bit)](http://package.mapr.com/tools/MapR-ODBC/MapR_Drill/MapRDrill_odbc_v1.0.0.1001/MapRDrillODBC32.msi)
-     * [MapR Drill ODBC Driver (64-bit)](http://package.mapr.com/tools/MapR-ODBC/MapR_Drill/MapRDrill_odbc_v1.0.0.1001/MapRDrillODBC64.msi)
-  2. Double-click the installer from the location where you downloaded it.
-  3. Click **Next.**
-  4. Select the check box to accept the terms of the License Agreement and click **Next**.
-  5. Verify or change the install location. Then, click **Next**.
-  6. Click **Install**.
-  7. When the installation completes, click **Finish**.
-  8. To verify the installation, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator**. Then, click the **Drivers** tab and verify that the MapR Drill ODBC Driver appears in the list of drivers that are installed on the computer.
-
-## The Tableau Data-connection Customization (TDC) File
-
-The MapR Drill ODBC Driver includes a file named `MapRDrillODBC.TDC`. The TDC file includes customizations that improve ODBC configuration and performance
-when using Tableau.
-
-### Installing the TDC File
-The MapR Drill ODBC driver installer automatically installs the TDC file if the installer can find the Tableau installation. If you installed the MapR Drill ODBC driver first and then installed Tableau, the TDC file is not installed automatically, and you need to install the TDC file manually. 
-
-**To install the MapRDrillODBC.TDC file manually:**
-
-  1. Click **Start > All Programs > MapR Drill ODBC Driver <version> (32|64-bit) > Install Tableau TDC File**. 
-  2. When the installation completes, press any key to continue.   
-For example, you can press the SPACEBAR key.
-
-If the installation of the TDC file fails, this is likely due to your Tableau repository being in location other than the default one.  In this case, manually copy the My Tableau Repository to C:\Users\<user>\Documents\My Tableau Repository. Repeat the procedure to install the MapRDrillODBC.TDC file manually.
-
-
-#### What's Next? Go to [Step 2. Configure ODBC Connections to Drill Data Sources]({{ site.baseurl }}/docs/configuring-connections-on-windows).

http://git-wip-us.apache.org/repos/asf/drill/blob/8f1c9a42/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/020-configuring-connections-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/020-configuring-connections-on-windows.md b/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/020-configuring-connections-on-windows.md
deleted file mode 100644
index 2fa0115..0000000
--- a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/020-configuring-connections-on-windows.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-title: "Configuring Connections on Windows"
-parent: "Using ODBC on Windows"
----
-Complete one of the following steps to create an ODBC connection on Windows to Drill data
-sources:
-
-  * Create a Data Source Name
-  * Create an ODBC Connection String
-
-**Prerequisite:** An Apache Drill installation must be [configured]({{ site.baseurl }}/docs/connect-a-data-source-introduction/) to access the data sources that you want to connect to.  For information about how to install Apache Drill, see [Install Drill]({{ site.baseurl }}/docs/install-drill).
-
-## Create a Data Source Name (DSN)
-
-Create a DSN that an application can use to connect to Drill data sources. If
-you want to create a DSN for a 32-bit application, you must use the 32-bit
-version of the ODBC Administrator to create the DSN.
-
-1. To launch the ODBC Administrator, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator**.  
-   
-    To launch the 32-bit version of the ODBC driver on a 64-bit machine, run:
-`C:\WINDOWS\SysWOW64\odbcad32.exe`.  
-    The ODBC Data Source Administrator window appears.  
-2. Create a system or user DSN on the **System DSN** or **User DSN** tab, respectively. A system DSN is available for all users who log in to the machine. A user DSN is available to the user who creates the DSN.  
-3. Click **Add**.  
-4. Select **MapR Drill ODBC Driver** and click **Finish**.  
-   The _MapR Drill ODBC Driver DSN Setup_ window appears.
-5. In the **Data Source Name** field, enter a name for the DSN.  
-6. Optionally, enter a description of the DSN in the Description field.
-7. In the Connection Type section, select one of the following connection types:  
-   * ZooKeeper Quorum  
-   * Direct to Drillbit  
-8. If you select **ZooKeeper Quorum**, provide values for the following properties:  
-   * Quorum  
-     A comma separated list of ZooKeeper nodes in the following format:  
-     `<host name/ip address> : <port number>, <host name/ip address> : <port number>, . . .`  
-   * Cluster ID  
-     Name of the drillbit cluster, drillbits1 by default. Check the `drill-override.conf` file for any cluster name changes.  
-
-    If you select Direct to Drillbit, provide the IP address or host name of the Drill server and the Drill listen port number, 31010 by default. Check the `drill-override.conf` file for any port changes.  
-9. In **Default Schema**, select the [default schema]({{site.baseurl}}/docs/configuring-connections-on-windows/#schema) to connect to.  
-10. Optionally, perform the following operations:  
-    * Update the [advanced properties]({{site.baseurl}}/docs/configuring-connections-on-windows/#advanced-properties) configuration.  
-    * Configure [logging options]({{site.baseurl}}/docs/configuring-connections-on-windows/#logging-options) to log types of events.  
-11. Click **OK** to save the DSN.
-
-## Configuration Options
-
-### Connection Type
-
-ODBC can connect directly to a Drillbit or to a ZooKeeper Quorum. Select your
-connection type based on your environment and Drillbit configuration.
-
-The following table lists the appropriate connection type for each scenario:
-
-<table ><tbody><tr><th >Scenario</th><th >Connection Type</th></tr><tr><td valign="top">Drillbit is running in embedded mode.</td><td valign="top">Direct to Drillbit</td></tr><tr><td valign="top">Drillbit is registered with the ZooKeeper in a testing environment.</td><td valign="top">ZooKeeper Quorum or Direct to Drillbit</td></tr><tr><td valign="top">Drillbit is registered with the ZooKeeper in a production environment.</td><td valign="top">ZooKeeper Quorum</td></tr></tbody></table> 
-
-#### Connection to Zookeeper Quorum
-
-When you choose to connect to a ZooKeeper Quorum, the ODBC driver connects to
-the ZooKeeper Quorum to get a list of available Drillbits in the specified
-cluster. Then, the ODBC driver submits a query after selecting a Drillbit. All
-Drillbits in the cluster process the query and the Drillbit that received the
-query returns the query results.
-
-![ODBC to Quorum]({{ site.baseurl }}/docs/img/ODBC_to_Quorum.png)
-
-In a production environment, you should connect to a ZooKeeper Quorum for a
-more reliable connection. If one Drillbit is not available, another Drillbit
-that is registered with the ZooKeeper quorum can accept the query.
-
-#### Direct Connection to Drillbit
-
-When you choose to connect directly to a Drillbit, the ODBC driver connects to
-the Drillbit and submits a query. If you connect directly to Drillbit that is
-not part of a cluster, the Drillbit that you connect to processes the query.
-If you connect directly to a Drillbit that is part of a cluster, all Drillbits
-in the cluster process the query. In either case, the Drillbit that the ODBC
-driver connected to returns the query results.
-
-![]({{ site.baseurl }}/docs/img/ODBC_to_Drillbit.png)
-
-### Catalog
-
-This value defaults to DRILL and cannot be changed.
-
-### Schema
-
-The Default Schema list contains the data sources that you have configured to
-use with Drill via the Drill Storage Plugin.
-
-Views that you create using the Drill Explorer do not appear under the schema
-associated with the data source type. Instead, the views can be accessed from
-the file-based schema that you selected when saving the view.
-
-### Advanced Properties
-
-The Advanced Properties field allows you to customize the DSN.  
-You can configure the values of the following advanced properties:
-
-<table ><tbody><tr><th >Property Name</th><th >Default Value</th><th >Description</th></tr><tr><td valign="top">HandshakeTimeout</td><td valign="top">5</td><td valign="top">An integer value representing the number of seconds that the driver waits to establish a connection before aborting. When set to 0, the driver does not abort connection attempts.</td></tr><tr><td valign="top">QueryTimeout</td><td valign="top">180</td><td valign="top">An integer value representing the number of seconds for the driver to wait before automatically stopping a query. When set to 0, the driver does not stop queries automatically.</td></tr><tr><td valign="top">TimestampTZDisplayTimezone</td><td valign="top">local</td><td valign="top">A string value that defines how the timestamp with timezone is displayed:<ul><li class="Body"><strong>local</strong>—Timestamps appear in the time zone of the user.</li><li class="Body"><strong>utc</strong>—Timestamps appear in Coordinated Universal Time (UTC).</li></ul
 ></td></tr><tr><td valign="top">ExcludedSchemas</td><td valign="top">sys, INFORMATION_SCHEMA</td><td valign="top">A list of schemas that should not appear in client applications such as Drill Explorer, Tableau, and Excel. Separate schemas in the list using a comma (,).</td></tr></tbody></table> 
-Separate each advanced property using a semicolon.
-
-For example, the following Advanced Properties string excludes the schemas
-named test and abc; sets the timeout to 30 seconds; and, sets the time zone to
-Coordinated Universal Time:  
-`HandshakeTimeout=30;QueryTimeout=30;TimestampTZDisplayTimezone=utc;ExcludedSchemas=test,abc`
-
-### Logging Options
-
-Configure logging to troubleshoot issues. To configure logging, click the
-Logging Options button on the ODBC DSN Setup dialog and then set a log level
-and a log path.
-
-If logging is enabled, the MapR Drill ODBC driver logs events in following log
-files in the log path that you configure:
-
-<table ><tbody><tr><th >Log File</th><th >Description</th></tr><tr><td valign="top">driver.log</td><td valign="top">A log of driver events.</td></tr><tr><td valign="top">drillclient.log</td><td valign="top">A log of the Drill client events.</td></tr></tbody></table> 
-
-#### Logging Levels
-
-Each logging level provides a different level of detail in the log files. The
-following log levels are available:
-
-<table ><tbody><tr><th >Logging Level</th><th >Description</th></tr><tr><td valign="top">OFF</td><td valign="top">Disables all logging.</td></tr><tr><td valign="top">FATAL</td><td valign="top">Logs severe error events that may cause the driver to stop running.</td></tr><tr><td valign="top">ERROR</td><td valign="top">Logs error events that may allow the driver to continue running.</td></tr><tr><td valign="top">WARNING</td><td valign="top">Logs events about potentially harmful situations.</td></tr><tr><td valign="top">INFO</td><td valign="top">Logs high-level events about driver processes.</td></tr><tr><td valign="top">DEBUG</td><td valign="top">Logs detailed events that may help to debug issues.</td></tr><tr><td colspan="1" valign="top">TRACE</td><td colspan="1" valign="top">Logs finer-grained events than the DEBUG level.</td></tr></tbody></table>
-
-## Create an ODBC Connection String
-
-If you want to connect to a Drill data source from an application that does
-not require a DSN, you can use an ODBC connection string.  
-The following table describes the properties that you can use in the
-connection string:
-
-<table ><tbody><tr><th >Property</th><th >Description</th></tr><tr><td valign="top"><a href="#advanced-properties">AdvancedProperties</a></td><td valign="top">Separate advanced properties using a semicolon (;), and then surround all advanced properties in a connection string using braces { and }.</td></tr><tr><td valign="top">Catalog</td><td valign="top">The name of the catalog, under which all of the schemas are organized. The catalog name is DRILL.</td></tr><tr><td valign="top"><a href="#connection-type"> ConnectionType</a></td><td valign="top">One of the following values:<br />• Direct—Connect to a Drill server using Host and Port properties in the connection string.<br />• ZooKeeper—Connect to a ZooKeeper cluster using ZKQuorum and ZKClusterID properties in the connection string.</td></tr><tr><td valign="top">DRIVER</td><td valign="top">The name of the installed driver: MapR Drill ODBC Driver<br />(Required)</td></tr><tr><td valign="top">Host</td><td valign="top">If the 
 ConnectionType property is set to Direct, indicate the IP address or hostname of the Drillbit server.</td></tr><tr><td valign="top">Port</td><td valign="top">If the ConnectionType property is set to Direct, indicate the port on which the Drillbit server is listening.</td></tr><tr><td valign="top">Schema</td><td valign="top">The name of the database schema to use when a schema is not explicitly specified in a query.<br />Note: Queries on other schemas can still be issued by explicitly specifying the schema in the query.</td></tr><tr><td valign="top">ZKClusterID</td><td valign="top">If the ConnectionType property is set to ZooKeeper, then use ZKClusterID to indicate the name of the Drillbit cluster to use.</td></tr><tr><td valign="top">ZKQuorum</td><td valign="top">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 (,).</td></tr></tbody></table>
-
-#### Connection String Examples
-
-The following is an example connection string for the Direct connection type:  
-
-        DRIVER=MapR Drill ODBC Driver;AdvancedProperties={HandshakeTimeout=0;QueryTimeout=0;TimestampTZDisplayTimezone=utc;ExcludedSchemas=sys,INFORMATION_SCHEMA;};Catalog=DRILL;Schema=hivestg;ConnectionType=Direct;Host=192.168.202.147;Port=31010
-
-The following is an example connection string for the Zookeeper connection
-type:  
-
-        DRIVER=MapR Drill ODBC Driver;AdvancedProperties={HandshakeTimeout=0;QueryTimeout=0;TimestampTZDisplayTimezone=utc;ExcludedSchemas=sys, INFORMATION_SCHEMA;};Catalog=DRILL;Schema=;ConnectionType=ZooKeeper;ZKQuorum=192.168.39.43:5181;ZKClusterID=drillbits1
-
-#### What's Next? Go to [Step 3. Connect to Drill Data Sources from a BI Tool]({{ site.baseurl }}/docs/connecting-to-odbc-data-sources).
-

http://git-wip-us.apache.org/repos/asf/drill/blob/8f1c9a42/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/030-connecting-to-data-sources.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/030-connecting-to-data-sources.md b/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/030-connecting-to-data-sources.md
deleted file mode 100644
index b778a27..0000000
--- a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/030-connecting-to-data-sources.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: "Connecting to ODBC Data Sources"
-parent: "Using ODBC on Windows"
----
-After you create the ODBC DSN, you can use ODBC on Windows to directly connect to data
-that is defined by a schema, such as Hive, and data that is self-describing.
-Examples of self-describing data include HBase, Parquet, JSON, CSV,and TSV.
-
-In some cases, you may want to use Drill Explorer to explore that data or to
-create a view before you connect to the data from a BI tool. For more
-information about Drill Explorer, see [Using Drill Explorer on Windows]({{ site.baseurl }}/docs/using-drill-explorer-on-windows) to browse data and create views.
-
-In an ODBC-compliant BI tool, use the ODBC DSN to create an ODBC connection
-with one of the methods applicable to the data source type:
-
-| Data Source Type               | ODBC Connection Method                                                                                                                                      |
-|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Hive                           | Connect to a table. Connect to the table using custom SQL. Use Drill Explorer to create a view. Then use ODBC to connect to the view as if it were a table. |
-| HBase, Parquet, JSON, CSV, TSV | Use Drill Explorer to create a view. Then use ODBC to connect to the view as if it were a table. Connect to the data using custom SQL.                      |
-  
-{% include startnote.html %}The default schema that you configure in the DSN may or may not carry over to an application’s data source connections. You may need to re-select the schema.{% include endnote.html %}
-
-

http://git-wip-us.apache.org/repos/asf/drill/blob/8f1c9a42/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/040-tableau-examples.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/040-tableau-examples.md b/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/040-tableau-examples.md
deleted file mode 100644
index 9b73096..0000000
--- a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/040-tableau-examples.md
+++ /dev/null
@@ -1,251 +0,0 @@
----
-title: "Tableau Examples"
-parent: "Using ODBC on Windows"
----
-You can generate reports in Tableau using ODBC connections to Drill data
-sources. Each example in this section takes you through the steps to create a
-DSN to a Drill data source and then access the data in Tableau 8.1.
-
-This section includes the following examples:
-
-  * Connecting to a Hive table  
-  * Using a view to connect to Hbase table data  
-  * Using custom SQL to connect to data in a Parquet file
-
-The steps and results of these examples assume pre-configured schemas and
-source data. You configure schemas as storage plugin instances on the Storage
-tab of the [Drill Web UI]({{ site.baseurl }}/docs/getting-to-know-the-drill-sandbox#storage-plugin-overview). Also, the examples assume you [enabled the DECIMAL data type]({{site.baseurl}}/docs/supported-data-types#enabling-the-decimal-type) in Drill.  
-
-## Example: Connect to a Hive Table in Tableau
-
-To access Hive tables in Tableau 8.1, connect to the Hive schema using a DSN
-and then visualize the data in Tableau.  
-{% include startnote.html %}This example assumes that there is a schema named hive.default which contains a table named student_hive.{% include endnote.html %}
-
-----------
-
-## Step 1: Create a DSN to a Hive Table
-
-In this step, we will create a DSN that accesses a Hive table.
-
-  1. To launch the ODBC Administrator, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator.**
-     The _ODBC Data Source Administrator _window appears.
-  2. On the **System DSN** tab, click **Add**.
-  3. Select **MapR Drill ODBC Driver** and click **Finish**.  
-     The _MapR Drill ODBC Driver DSN Setup_ window appears.
-  4. Enter a name for the data source.
-  5. Specify the connection type based on your requirements. The connection type provides the DSN access to Drill Data Sources.  
-In this example, we are connecting to a Zookeeper Quorum.
-  6. In the **Schema** field, select the Hive schema.
-     In this example, the Hive schema is named hive.default.
-     ![]({{ site.baseurl }}/docs/img/Hive_DSN.png)
-  7. Click **OK** to create the DSN and return to the ODBC Data Source Administrator window.
-  8. Click **OK** to close the ODBC Data Source Administrator.
-
-----------
-
-## Step 2: Connect to Hive Tables in Tableau
-
-Now, we can connect to Hive tables.
-
-  1. In Tableau, click **Data > Connect to Data**.
-  2. In the _On a server_ section, click **Other Databases (ODBC**).  
-     The *Generic ODBC Connection* dialog appears.
-  3. In the *Connect Using* section, select the DSN that connects to the Hive table.   
--or-  
-To create a connection without an existing DSN, select the Driver option,
-select the MapR Drill ODBC driver from the list and click **Connect.** Then,
-configure the connection to the Hive table and click **OK**.
-  4. In the **Schema** field, select the Hive schema.  
-     In this example, the Hive schema is named hive.default.
-  5. In the _Table_ section, verify that **Single Table** is selected and then click the Search icon.  
-     A list of tables appears.
-  6. Select the table from the list and click **Select**.   
-     In this example, the table name is student_hive.
-  7. Click **OK** to complete the connection.  
-     ![]({{ site.baseurl }}/docs/img/ODBC_HiveConnection.png)
-  8. In the _Data Connection_ dialog, click **Connect Live**.
-
-----------
-
-## Step 3. Visualize the Data in Tableau
-
-Once you connect to the data, the columns appear in the Data window. To
-visualize the data, drag fields from the Data window to the workspace view.
-
-For example, you can visualize the data in this way:
-
-![]({{ site.baseurl }}/docs/img/student_hive.png)
-
-## Example: Connect to Self-Describing Data in Tableau
-
-You can connect to self-describing data in Tableau in the following ways:
-
-  1. Use Drill Explorer to explore the self-describing data sources, create a Drill view, and then use ODBC to access the view in Tableau as if it were a table. 
-  2. Use Tableau’s Custom SQL to query the self-describing data directly. 
-
-### Option 1. Using a View to Connect to Self-Describing Data
-
-The following example describes how to create a view of an HBase table and
-connect to that view in Tableau 8.1. You can also use these steps to access
-data for other sources such as Hive, Parquet, JSON, TSV, and CSV.
-
-{% include startnote.html %}This example assumes that there is a schema named hbase that contains a table named s_voters and a schema named dfs.default that points to a writable location.{% include endnote.html %}
-
-#### Step 1. Create a View and a DSN
-
-In this step, we will use the ODBC Administrator to access the Drill Explorer
-where we can create a view of an HBase table. Then, we will use the ODBC
-Administrator to create a DSN that connects to the view.
-
-  1. To launch the ODBC Administrator, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator**.  
-     The _ODBC Data Source Administrator_ window appears.
-  2. On the System DSN tab, click **Add**.
-  3. Select **MapR Drill ODBC Driver** and click **Finish**.
-     The _MapR Drill ODBC Driver DSN Setup_ window appears.
-  4. Specify the Connection Type based on your requirements.
-     The connection type provides the DSN access to a Drillbit. For more
-information, see [Connection Type]({{ site.baseurl }}/docs/configuring-connections-on-windows/#connection-type).
-  5. Click **Drill Explorer** to start exploring the data.
-     The Drill Explorer dialog appears. You can use the Browse tab to visually
-explore the metadata and data available from Drill data sources. Advanced
-users can use SQL tab to type in SQL manually to explore the data and save the
-SQL query as a view.
-  6. Select the schema that you want to create a view for.
-      ![]({{ site.baseurl }}/docs/img/Hbase_Browse.png)        
-     Drill Explorer displays the metadata and column families for the selected
-HBase table.
-  7. To create a view of the HBase table, click the **SQL** tab.  
-     By default, the View Definition SQL field contains: `SELECT * FROM
-<schema>.<table>`
-  8. To create the view, enter SQL in the _View Definition SQL_ section and then click **Preview** to verify that the results are as expected.   
-      ![]({{ site.baseurl }}/docs/img/ODBC_HbasePreview2.png)
-     In this example, the following SQL was entered:
-       
-        SELECT cast(row_key as integer) voter_id, convert_from(voter.onecf.name,
-        'UTF8') name, cast(voter.twocf.age as integer) age,
-        cast(voter.twocf.registration as varchar(20)) registration,
-        cast(voter.threecf.contributions as decimal(6,2)) contributions,
-        cast(voter.threecf.voterzone as integer)
-        voterzone,cast(voter.fourcf.create_date as timestamp) create_time FROM
-        hbase.voter
-
-     HBase does not contain type information, so you need to cast the data in Drill
-Explorer. For information about SQL query support, see the [SQL Reference]({{ site.baseurl }}/docs/sql-reference).
-  9. To save the view, click **Create As**.
-  10. Specify the schema where you want to save the view, enter a name for the view, and click **Save**.  
-
-       ![]({{ site.baseurl }}/docs/img/HbaseViewCreation0.png)
-
-  11. Close the Drill Explorer to return to the _MapR Drill ODBC Driver DSN Setup _window.  
-      Now that we have created the view, we can create a DSN that can access the
-view.
-  12. Enter a data source name and select the schema where you saved the view.  
-      In this example, we saved the view to dfs.default.        
-       ![]({{ site.baseurl }}/docs/img/HbaseViewDSN.png)
-  13. Click **OK** to create the DSN and return to the _ODBC Data Source Administrator_ window.
-  14. Click **OK** to close the ODBC Data Source Administrator.
-
-#### Step 2. Connect to the View from Tableau
-
-Now, we can connect to the view in Tableau.
-
-  1. In Tableau, click **Data > Connect to Data**.
-  2. In the _On a server_ section, click **Other Databases (ODBC)**.  
-     The *Generic ODBC Connection* dialog appears.
-  3. In the *Connect Using* section, select the DSN that connects to the schema that contains the view that you created.   
-     -or-  
-     To create a connection without an existing DSN, select the **Driver** option, select the **MapR Drill ODBC Driver** from the list and click **Connect**. Then, configure the connection using the steps in step 1 and click **OK**.In this example, we created SQLView-DrillDataSource to access the view.
-  4. In the **Schema** field, select the schema that contains the views that you created in Drill Explorer.  
-     In this example, we saved the view to the dfs_default schema.
-  5. In the *Table* section, verify that **Single Table** is selected and then click the Search icon.  
-     A list of views appears.
-  6. Select the view from the list and click **Select**.   
-     In this example, we need to select hbase_s_voter.  
-      ![]({{ site.baseurl }}/docs/img/SelectHbaseView.png)
-  7. Click **OK** to complete the connection.   
-      ![]({{ site.baseurl }}/docs/img/ODBC_HbaseView.png)
-  8. In the _Data Connection dialog_, click **Connect Live**.
-
-#### Step 3. Visualize the Data in Tableau
-
-Once you connect to the data in Tableau, the columns appear in the Data
-window. To visualize the data, drag fields from the Data window to the
-workspace view.
-
-For example, you can visualize the data in this way:
-
-![]({{ site.baseurl }}/docs/img/VoterContributions_hbaseview.png)
-
-### Option 2. Using Custom SQL to Access Self-Describing Data
-
-The following example describes how to use custom SQL to connect to a Parquet
-file and then visualize the data in Tableau 8.1. You can use the same steps to
-access data from other sources such as Hive, HBase, JSON, TSV, and CSV.
-
-{% include startnote.html %}This example assumes that there is a schema named dfs.default which contains a parquet file named region.parquet.{% include endnote.html %}
-
-#### Step 1. Create a DSN to the Parquet File and Preview the Data
-
-In this step, we will create a DSN that accesses files on the DFS. We will
-also use Drill Explorer to preview the SQL that we want to use to connect to
-the data in Tableau.
-
-  1. To launch the ODBC Administrator, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator.**   
-     The *ODBC Data Source Administrator* window appears.
-  2. On the **System DSN** tab, click **Add**.
-  3. Select **MapR Drill ODBC Driver** and click **Finish**.  
-     The _MapR Drill ODBC Driver DSN Setup_ window appears.
-  4. Enter a data source name.
-  5. Specify the connection type based on your requirements. See [Connection Type]({{ site.baseurl }}/docs/configuring-connections-on-windows/#connection-type) for more information.  
-     The connection type provides the DSN access to a Drillbit.  
-     In this example, we will connect to a Zookeeper Quorum.
-  6. In the _Schema_ section, select the schema associated with the data source that contains the Parquet file that you want to access. Then, click **OK**.  
-     In this example, the Parquet file is available in the dfs.default schema.  
-      ![]({{ site.baseurl }}/docs/img/Parquet_DSN.png)  
-     You can use this DSN to access multiple files from the same schema.  
-     In this example, we plan to use the Custom SQL option to connect to data in Tableau. You can use Drill Explorer to preview the results of custom SQL before you enter the SQL in Tableau.
-  7. If you want to preview the results of a query, click **Drill Explorer**.
-    1. On the **Browse** tab, navigate to the file that you want. 
-    2. Click the **SQL** tab.  
-       The SQL tab will include a default query to the file you selected on the Browse tab. You can use the SQL tab to preview the results of various queries until you achieve the expected result.
-    3. Enter the query that you want to preview and then click **Preview**.  
-       ![]({{ site.baseurl }}/docs/img/Parquet_Preview.png)  
-       You can copy this query to file so that you can use it in Tableau.
-    4. Close the Drill Explorer window. 
-  8. Click **OK** to create the DSN and return to the _ODBC Data Source Administrato_r window.
-  9. Click **OK** to close the ODBC Data Source Administrator.
-
-#### Step 2. Connect to a Parquet File in Tableau using Custom SQL
-
-Now, we can create a connection to the Parquet file using the custom SQL.
-
-  1. In Tableau, click **Data > Connect to Data**.
-  2. In the _On a server_ section, click **Other Databases (ODBC).**
-     The *Generic ODBC Connection* dialog appears.
-  3. In the *Connect Using* section, select the DSN that connects to the data source.  
-     In this example, Files-DrillDataSources was selected.
-  4. In the *Schema* section, select the schema associated with the data source.  
-     In this example, dfs.default was selected.
-  5. In the *Table* section, select **Custom SQL**.
-  6. Enter the SQL query.  
-     In this example, the following SQL query was entered: 
-     
-         SELECT CAST(R_NAME as varchar(20))Country,
-         CAST(R_COMMENT as varchar(200))Comments, R_RegionKey 
-         FROM `dfs`.`default`.`./opt/mapr/drill/drill-1.0.0.BETA1/sample-data/region.parquet`  
-
-     {% include startnote.html %}The path to the file depends on its location in your file system.{% include endnote.html %} 
-
-  7. Click **OK** to complete the connection.  
-     ![]({{ site.baseurl }}/docs/img/ODBC_CustomSQL.png)
-  8. In the _Data Connection dialog_, click **Connect Live**.
-
-#### Step 3. Visualize the Data in Tableau
-
-Once you connect to the data, the fields appear in the Data window. To
-visualize the data, drag fields from the Data window to the workspace view.
-
-For example, you can visualize the data in this way:
-![]({{ site.baseurl }}/docs/img/RegionParquet_table.png)
-

http://git-wip-us.apache.org/repos/asf/drill/blob/8f1c9a42/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/050-using-drill-explorer-on-windows.md
----------------------------------------------------------------------
diff --git a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/050-using-drill-explorer-on-windows.md b/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/050-using-drill-explorer-on-windows.md
deleted file mode 100644
index 3d84978..0000000
--- a/_docs/odbc-jdbc-interfaces/using-odbc-on-windows/050-using-drill-explorer-on-windows.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: "Using Drill Explorer on Windows"
-parent: "Using ODBC on Windows"
----
-Drill Explorer is a simple user interface that is embedded within the ODBC
-DSN. Drill Explorer enables users to understand the metadata and data before
-visualizing the data in a BI tool. Use Drill Explorer to browse Drill data
-sources, preview the results of a SQL query, and create a view that you can
-query.
-
-The Browse tab of Drill Explorer allows you to view metadata for each schema
-that you can access with Drill. The SQL tab allows you to preview the results
-of custom queries and save the results as a view.
-
-**To Browse Data:**
-
-  1. To launch the ODBC Administrator, click
-     **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator**.
-  2. Click the **User DSN** tab or the **System DSN** tab and then select the DSN that corresponds to the Drill data source that you want to explore.
-  3. Click **Configure**.  
-     The _MapR Drill ODBC Driver DSN Setup_ dialog appears.
-  4. Click **Drill Explorer**.
-  5. In the **Schemas** section on the **Browse** tab, navigate to the the data source that you want to explore.
-
-**To Create a View**:
-
-  1. To launch the ODBC Administrator, click **Start > All Programs > MapR Drill ODBC Driver 1.0 (32|64-bit) > (32|64-bit) ODBC Administrator**.
-  2. Click the **User DSN** tab or the **System DSN** tab and then select the DSN that corresponds to the Drill data source that you want to explore.
-  3. Click **Configure**.  
-     The _MapR Drill ODBC Driver DSN Setup_ dialog appears.
-  4. Click **Drill Explorer**.
-  5. In the **Schemas** section on the **Browse** tab, navigate to the the data source that you want to create a view for.  
-     After you select a data souce, the metadata and data displays on the Browse tab and the SQL that is used to access the data displays on the SQL tab.
-  6. Click the **SQL** tab.
-  7. In the **View Definition SQL** field, enter the SQL query that you want to create a view for.
-  8. Click **Preview**.   
-      If the results are not as expected, you can edit the SQL query and click
-Preview again.
-  9. Click **Create As**.  
-     The _Create As_ dialog displays.
-  10. In the **Schema** field, select the schema where you want to save the view.
-      You can save views only to file-based schemas.
-  11. In the **View Name** field, enter a descriptive name for the view.
-      Do not include spaces in the view name.
-  12. Click **Save**.   
-      The status and any error message associated with the view creation displays in
-the Create As dialog. When a view saves successfully, the Save button changes
-to a Close button.
-  13. Click **Close**.
-