gistfile1.txt

1.0.3 ========================================================================

Released 2020-05-06

Enhancements & New Features

 * [NEOJ-66] Java driver logging

   You can now log Neo4j Java driver activity by using the 
   EnableJavaDriverLogging connection URL option. The driver uses the
   following components to allow Neo4j Java driver activity to be logged: 
   - log4j-1.2.17
   - slf4j-api-1.7.28
   - slf4j-log4j12-1.7.28  
   
   For more information, see the Installation and Configuration Guide.

 * [NEOJ-84] Aggregate passdown

   The driver now supports passing down simple queries involving aggregate
   functions to the server for execution. This improves performance for these
   queries. For more information, see the Installation and 
   Configuration Guide.

 * [NEOJ-86] Sort passdown

   The driver now supports sort passdown for SQL queries. This improves
   performance for queries that involve sorting data.

 * [NEOJ-112] Upgraded driver dependency

   The driver now uses the Neo4j Java driver 4.0.1 dependency. Previously, it
   used Neo4j Java Driver 4.0.0.

 * [NEOJ-115] Support for EXTRACT scalar function

   You can now use the EXTRACT scalar function with the following data types:
   - YEAR
   - MONTH
   - DAY
   - HOUR
   - MINUTE
   - SECOND


Resolved Issues
The following issues have been resolved in Simba Neo4j BI Connector 1.0.3.

 * [NEOJ-70] SQL_TIMESTAMP values with nanoseconds fractional seconds
   precision are truncated to microseconds fractional seconds precision.

 * [NEOJ-70] Fractional seconds precision is not included for SQL_TIME values.
   
   This issue has been resolved. The driver now sets the maximum fractional 
   seconds precision for SQL_TIME values as milliseconds. For information on 
   the limitation of fractional seconds precision for SQL_TIME type values, 
   please see the Known Issues section below.
   
 * [NEOJ-117] The driver returns the error "A logic error occurred: null" for
   invalid cast operations.
   
   This issue has been resolved. The driver now returns the error "Invalid
   character value for cast specification".
   
 * [NEOJ-118] The maximum length of an identifier is 255 characters.
 
   This issue has been resolved. You can now configure this limitation with
   the MaxIdentifierLen connection URL option. For more information, see the
   Installation and Configuration Guide.
   
 * [NEOJ-116] When the driver retrieves results, the TOP or LIMIT value from
   the outer query is chosen as the value to be passed down to Neo4j.
 
   This issue has been resolved. The TOP or LIMIT clause condition specified
   in sub-queries is now taken into account when passing a query down to
   Neo4j.   


Known Issues
The following are known issues that you may encounter due to limitations in
the data source, the driver, or an application.

 * The driver handles SUM(NULL) differently from the Neo4j server. The driver
   returns NULL for SUM(NULL), while the Neo4j server returns 0 for SUM(NULL).
   This might result in a discrepancy between queries that are passed down and
   queries that are resolved by the driver. For more information about
   aggregate function passdown, see the Installation and Configuration Guide.

 * [NEOJ-70] If a property contains time values that have fractional second
   precision beyond milliseconds, the value truncates to milliseconds
   fractional seconds precision. 
   
   For example, a time value of 13:59:23.123456 in the Neo4j database is
   represented by the driver in the result set as 13:59:23.123.
   
   A SQL query that filters on a time value stored in the Neo4j server with
   fractional seconds precision beyond milliseconds results in an empty result
   set.

 * [NEOJ-84] Aggregate values calculated by the server can be different than
   values calculated by the driver. For more information, see the Installation
   and Configuration Guide. 
   
 * [NEOJ-107] If you connect to a single-instance Neo4j 3.5 server using
   Tableau, the driver becomes unresposive during the query execution stage
   and eventually returns a timeout error.
   
   This occurs because you are connecting to a Neo4j 3.5 single-instance
   server that does not have a routing table, and therefore connection should
   only be attempted using the bolt scheme. To resolve this,
   set the connection property StrictlyUseBoltScheme as "true". For more 
   information, see the Installation and Configuration Guide.