pvillard31 commented on PR #7569:
URL: https://github.com/apache/nifi/pull/7569#issuecomment-1664204483

   Just for tracking.
   
   ### Version 3.14.0 (July 27, 2023)
   
   **BCR (Behavior Change Release) Change**
   
   Fixed an issue where, under certain conditions, the JDBC driver could retry 
HTTP requests indefinitely. 
   Previously, during an outage the JDBC driver would retry the failed HTTP 
call continuously until the request succeeds or until someone force kills the 
operation.
   
   With this change, disables infinite HTTP retries originating from execute 
and executeQuery calls. Now, the JDBC driver limits HTTP retries to seven, by 
default. Customers can set the maxHttpRetries session parameter to customize 
the maximum number of retries. Customers can set maxHttpRetries=0 to remove the 
retry limit, but doing so runs the risk of the JDBC driver infinitely retrying 
failed HTTP calls.
    
   **New Features and Updates**
   
   - Added the CLIENT_OUT_OF_BAND_TELEMETRY_ENABLED session property to allow 
you to disable OOB telemetry.
   - Improved handling for locatorsUpdateCopy() function calls. Now, the driver 
returns FALSE instead of throwing an exception.
   - Updated handling for 400 Bad Request errors for S3 clients and added the 
putGetMaxRetries connection property to configure the maximum number of retries 
for PUT/GET exceptions for storage clients (default: 7).
   - Added support for httpMaxRetries in 
DefaultResultStreamProvider.getResultChunk()to improve chunk downloading 
performance.
   
   **Bug Fixes**
   
   - Fixed an issue where the driver incorrectly through null pointer 
exceptions (NPEs) when calling driver.getPropertyInfo().
   - Fixed an issue where reader.LoadNextBatch() would occasionally throw a 
ClosedByInterruptException when reading from the arrow stream.
   - Fixed an issue where the JDBC driver used the wrong proxy settings for S3 
clients.
   - Fixed an issue where the downloadStream() function disallowed filenames 
containing Japanese characters.
   - Fix an issue where '~' was not allowed in PUT/GET file paths.
   - Fixed an issue where the driver would through an InvalidPathException when 
a Windows file path included the file:// prefix for logging configuration files.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to