README
     Progress(R) DataDirect(R)
     Progress(R) DataDirect Connect XE(R) for JDBC(TM) for Impala(TM) Driver
     Release 5.1.4
     May 2016


***********************************************************************
Copyright (C) 1994-2016 Progress and/or its 
subsidiaries or affiliates. All Rights Reserved.

***********************************************************************


CONTENTS

Requirements
Installation Directory
Changes since Service Pack 4
Changes for Service Pack 4
Features
Notes, Known Problems, and Restrictions
Documentation
Installed Files


     Requirements

Java SE 5 or higher must be installed and the JVM must be defined on your system
path.


     Installation Directory

The default installation directory for the driver is:

* Windows:
  C:\Program Files\Progress\DataDirect\JDBC_51

* UNIX/Linux:
  /opt/Progress/DataDirect/JDBC_51
  Note: For UNIX/Linux, if you do not have access to "/opt", your user's
  directory should be used in place of this directory.


     Changes since Service Pack 4

Certifications
--------------
The driver has been certified with Cloudera Impala 2.2 and 2.3.

Statement Pooling
-----------------
The driver no longer registers the Statement Pool Monitor as a JMX MBean by
default. To register the Statement Pool Monitor and manage statement pooling with
standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
property must be set to true. See "Notes, Known Problems, and Restrictions" for
details.


     Changes for Service Pack 4

Certifications
--------------
The driver has been certified with Cloudera Impala 2.0 and 2.1.

Data Types
----------
The driver has been enhanced to support the Char and Vachar data type with
Cloudera Impala 2.1 and higher.

Result Set Holdability
----------------------
Support for result set holdability has been added to the driver. 


     Features

The driver supports standard SQL query language for read-write access to
Cloudera Impala data stores, versions 1.3 and higher. By using DataDirect's Wire
Protocol technology, the driver eliminates the need for client libraries,
improving response time and throughput. 

* The driver supports all JDBC Core functions.

* The driver supports the core SQL-92 grammar.

* The driver supports the following data types:
  - BIGINT        maps to     BIGINT
  - BOOLEAN       maps to     BOOLEAN
  - CHAR          maps to     CHAR
  - DECIMAL       maps to     DECIMAL
  - DOUBLE        maps to     DOUBLE
  - FLOAT         maps to     REAL
  - INT           maps to     INTEGER
  - SMALLINT      maps to     SMALLINT
  - STRING        maps to     VARCHAR (or LONGVARCHAR)
  - TIMESTAMP     maps to     TIMESTAMP
  - TINYINT       maps to     TINYINT
  - VARCHAR       maps to     VARCHAR

* The driver package includes the following components:
  - DataDirect Connection Pool Manager
  - DataDirect Statement Pool Monitor
  - DataDirect Test for JDBC
  - DataDirect Spy for JDBC


     Notes, Known Problems, and Restrictions

The following are notes, known problems, and restrictions with the driver.

* The RegisterStatementPoolMonitorMBean connection property registers the
  Statement Pool Monitor as a JMX MBean when statement pooling has been enabled
  with MaxPooledStatements. This allows you to manage statement pooling with
  standard JMX API calls and to use JMX-compliant tools, such as JConsole.
  - Valid values are true | false
  - If set to true, the driver registers an MBean for the statement pool monitor
    for each statement pool. This gives applications access to the Statement
    Pool Monitor through JMX when statement pooling is enabled.
  - If set to false, the driver does not register an MBean for the Statement Pool
    Monitor for any statement pool.
  - Registering the MBean exports a reference to the Statement Pool Monitor. The
    exported reference can prevent garbage collection on connections if the
    connections are not properly closed. When garbage collection does not take
    place on these connections, out of memory errors can occur.
  - The default is false.
  - The data type is boolean.

* Cloudera Impala is not designed for OLTP workloads and does not offer
  row-level updates or deletes. Cloudera Impala is instead designed for batch
  type jobs over large data sets with high latency.

* Cloudera Impala does not support transactions, and by default, the driver
  reports that transactions are not supported. However, some applications will 
  not operate with a driver that reports transactions are not supported. The
  TransactionMode connection property allows you to configure the driver to
  report that it supports transactions. In this mode, the driver ignores
  requests to enter manual commit mode, start a transaction, or commit a 
  transaction and return success. Requests to rollback a transaction return an
  error regardless of the transaction mode specified.

* Cloudera Impala Functional Limitations
  - No support for transactions
  - No support for canceling a running query
  - No support for row-level updates or deletes
  - No support for stored procedures
  - No support for auto-generated keys

* Cloudera Impala uses a subset of SQL and HiveQL, which provides much of the
  functionality of SQL, and therefore has some differences and limitations.
  - Column values and parameters are always nullable.
  - No support for row-level updates or deletes
  - Subqueries are supported, but they can only exist in the FROM and WHERE
    clauses.
  - No support for stored procedures
  - No ROWID support
  - No support for materialized views
  - No support for synonyms
  - Primary and foreign keys are not supported.
  - Support for indexes is incomplete.
  - A single quote within a string literal must be escaped using a \ instead
    of using a single quote.
  For more information, refer to the Impala SQL Language Reference: 
  http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/
  latest/topics/impala_langref.html

* For UNIX users: If you receive an error message when executing any DataDirect
  for JDBC shell script, make sure that the file has EXECUTE permission. To do
  this, use the chmod command. For example, to grant EXECUTE permission to the
  testforjdbc.sh file, change to the directory containing testforjdbc.sh and
  enter: chmod +x testforjdbc.sh

* The driver allows PreparedStatement.setXXX methods and ResultSet.getXXX
  methods on Clob data types, in addition to the functionality described in
  the JDBC specification. The supported conversions typically are the same as
  those for LONGVARCHAR, except where limited by database support.

* The Performance Tuning Wizard is not available with the driver. For
  information on tuning the driver for performance, see the "Performance
  Considerations" topic in the help system.

* Internet Explorer with the Google Toolbar installed sometimes displays the
  following error when the browser is closed: "An error has occurred in the
  script on this page." This is a known issue with the Google Toolbar and has
  been reported to Google. When closing the driver's help system, this error may
  display.


     Documentation

The PROGRESS DATADIRECT FOR JDBC FOR IMPALA DRIVER USER'S GUIDE is available as
an HTML help system and as a PDF.

* The HTML version of the USER'S GUIDE is installed in the ImpalaHelp
  subdirectory of your product installation directory. This help system is also
  available on the Progress DataDirect Web site:
  https://www.progress.com/resources/documentation/by-data-source

* The PDF version of the USER'S GUIDE is available on the Progress DataDirect
  Web site:
  https://www.progress.com/resources/documentation/by-data-source


     Installed Files

When you extract the contents of the installation download package to your
installer directory, you will notice the following files that are required to
install the driver:

*  Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.exe
   - PROGRESS_DATADIRECT_JDBC_IMPALA_5.1.4_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_COMMON_5.1.4_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_DOCUMENTATION_5.1.4_INSTALL.iam.zip

*  Non-Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.jar
   - PROGRESS_DATADIRECT_JDBC_IMPALA_5.1.4_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_COMMON_5.1.4_INSTALL.iam.zip
   - PROGRESS_DATADIRECT_JDBC_DOCUMENTATION_5.1.4_INSTALL.iam.zip

When you install the driver, the installer creates the following directories and
files in the product installation directory in the default installation
directory or in an installation directory you specify, represented by
INSTALL_DIR.


INSTALL_DIR/:
-------------
LicenseTool.jar            Product license file manager

DDProcInfo.exe             Windows executable to start the Processor Information
                           Utility

DDProcInfo                 UNIX/Linux script to start the Processor Information
                           Utility


INSTALL_DIR/Examples/Bulk/:
---------------------------
Load From File/bulkLoadFileDemo.java
                           Java source example for bulk loading from a CSV file

Load From File/load.txt    Sample data for the example

Streaming/bulkLoadStreamingDemo.java
                           Java source example for bulk loading from a result
                           set

Threaded Streaming/bulkLoadThreadedStreamingDemo.java
                           Java source example for multi-threaded bulk loading
                           from a result set

Threaded Streaming/README.txt
                           Instructions on how to use the thread.properties file

Threaded Streaming/thread.properties
                           Properties file for the example


INSTALL_DIR/Examples/Connector/:
--------------------------------
ConnectorSample.ear        J2EE Application Enterprise Archive file containing
                           the ConnectorSample application 

connectorsample.htm        USING DATADIRECT CONNECT FOR JDBC RESOURCE ADAPTERS
                           document

graphics/*.*               Images referenced by the USING DATADIRECT CONNECT FOR
                           JDBC RESOURCE ADAPTERS document

src/ConnectorSample.jsp    Source for the JavaServer Page used to access the
                           ConnectorSample application

src/connectorsample/ConnectorSample.java     
                           Java source file defining the remote interface for
                           the ConnectorSample EJB

src/connectorsample/ConnectorSampleBean.java  
                           Java source file defining the home interface for the
                           ConnectorSample EJB

src/connectorsample/ConnectorSampleHome.java  
                           Java source file containing the implementation for
                           the ConnectorSample EJB


INSTALL_DIR/Examples/JNDI/:
---------------------------
JNDI_FILESYSTEM_Example.java
                           Example Java(TM) source file

JNDI_LDAP_Example.java     Example Java source file


INSTALL_DIR/Examples/SforceSamples/:
------------------------------------
buildsamples.bat           Batch file to build the Salesforce example

buildsamples.sh            Shell script to build the Salesforce example
 
ddlogging.properties       Logging properties file

runsalesforceconnectsample.bat
                           Batch file to run the Salesforce example

runsalesforceconnectsample.sh
                           Shell script to run the Salesforce example

bin/com/ddtek/jdbc/samples/SalesforceConnectSample.class
                           Java example class

bin/com/ddtek/jdbc/samples/SampleException.class
                           Java example class

src/com/ddtek/jdbc/samples/SalesforceConnectSample.java
                           Java source example


INSTALL_DIR/Help/: 
------------------
ImpalaHelp/index.html      Driver HTML help system entry file

ImpalaHelp/*               Support files and folders for the driver help system


INSTALL_DIR/install/: 
---------------------
.psc_dd_inst_reg.xml       Support file for the installation logs

logs/*.*                   Log file generated upon installing or uninstalling


INSTALL_DIR/jre/:
-----------------
*.*                        Files associated with the driver. Installed only when
                           installing on Windows with the Windows executable
                           file.


INSTALL_DIR/lib/:
-----------------
impala.jar                 Impala Driver and DataSource classes


INSTALL_DIR/NOTICES/:
---------------------
JDBC for Impala v5.1.4 notices.txt
                           Third party agreement information


INSTALL_DIR/pool manager/:
--------------------------
pool.jar                   All DataDirect Connection Pool Manager classes


INSTALL_DIR/READMES/:
---------------------
JDBC for Impala v5.1.4 readme.txt
                           This file


INSTALL_DIR/testforjdbc/:
-------------------------
Config.txt                 Configuration file for DataDirect Test

ddlogging.properties       Logging properties file

testforjdbc.bat            Batch file to start DataDirect Test

testforjdbc.sh             Shell script to start DataDirect Test

lib/testforjdbc.jar        DataDirect Test classes


INSTALL_DIR/uninstall/:
-----------------------
.com.zerog.registry.xml    Support file for the uninstaller

.psc_dd_uninst_reg.xml     Support file for the uninstaller

InstallScript.iap_xml      Support file for the uninstaller

installvariables.properties
                           Support file for the Windows uninstaller

uninstall_Progress_DataDirect_for_JDBC_5.1_SP4.exe
                           Windows uninstaller

uninstall_Progress_DataDirect_for_JDBC_5.1_SP4.lax
                           Support file for the Windows uninstaller

uninstaller.jar            Java uninstaller

resource/*.*               Resource files for the Windows uninstaller


3 May 2016
=============
End of README