ASF GitHub Bot commented on HAWQ-1095:

Github user lisakowen commented on a diff in the pull request:

    --- Diff: clientaccess/g-database-application-interfaces.html.md.erb ---
    @@ -1,8 +1,96 @@
    -title: ODBC/JDBC Application Interfaces
    +title: HAWQ Database Drivers and APIs
    +You may want to connect your existing Business Intelligence (BI) or 
Analytics applications with HAWQ. The database application programming 
interfaces most commonly used with HAWQ are the Postgres and ODBC and JDBC APIs.
    -You may want to deploy your existing Business Intelligence (BI) or 
Analytics applications with HAWQ. The most commonly used database application 
programming interfaces with HAWQ are the ODBC and JDBC APIs. 
    +HAWQ provides the following connectivity tools for connecting to the 
    +  - ODBC driver
    +  - JDBC driver
    +  - `libpq` - PostgreSQL C API
    +## <a id="dbdriver"></a>HAWQ Drivers
    +ODBC and JDBC drivers for HAWQ are available as a separate download from 
Pivotal Network [Pivotal 
    +### <a id="odbc_driver"></a>ODBC Driver
    +The ODBC API specifies a standard set of C interfaces for accessing 
database management systems.  For additional information on using the ODBC API, 
refer to the [ODBC Programmer's 
    +HAWQ supports the DataDirect ODBC Driver. Installation instructions for 
this driver are provided on the Pivotal Network driver download page. Refer to 
 for HAWQ-specific ODBC driver information.
    +#### <a id="odbc_driver_connurl"></a>Connection Data Source
    +The information required by the HAWQ ODBC driver to connect to a database 
is typically stored in a named data source. Depending on your platform, you may 
 or [command 
 tools to create your data source definition. On Linux, ODBC data sources are 
typically defined in a file named `odbc.ini`. 
    +Commonly-specified HAWQ ODBC data source connection properties include:
    +| Property Name                                                    | Value 
    +| Database | name of the database to which you want to connect |
    +| Driver   | full path to the ODBC driver library file                     
    +| HostName              | HAWQ master host name                            
    +| MaxLongVarcharSize      | maximum size of columns of type long varchar   
    +| Password              | password used to connect to the specified 
    +| PortNumber              | HAWQ master database port number               
    +Refer to [Connection Option 
 for a list of ODBC connection properties supported by the HAWQ DataDirect ODBC 
    +Example HAWQ DataDirect ODBC driver data source definition:
    +``` shell
    +Description=DataDirect 7.1 Greenplum Wire Protocol - for HAWQ
    +The first line, `[HAWQ-201]`, identifies the name of the data source.
    +ODBC connection properties may also be specified in a connection string 
identifying either a data source name, the name of a file data source, or the 
name of a driver.  A HAWQ ODBC connection string has the following format:
    +``` shell
    --- End diff --
    i think the driver name is the full path to the driver library.  this will 
differ based on what the user enters for the install location when they run the 
install script.  it is not a set driver name like with jdbc.

> enhance database driver and API documentation
> ---------------------------------------------
>                 Key: HAWQ-1095
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1095
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Lisa Owen
>            Assignee: David Yozie
>            Priority: Minor
>             Fix For:
> docs contain very brief references to JDBC/ODBC and none at all to libpq.  
> add more content in these areas.

This message was sent by Atlassian JIRA

Reply via email to