Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-11905 Update snowflake-jdbc to 3.14.0 #7569

Closed
wants to merge 1 commit into from
Closed

NIFI-11905 Update snowflake-jdbc to 3.14.0 #7569

wants to merge 1 commit into from

Conversation

mr1716
Copy link
Contributor

@mr1716 mr1716 commented Aug 3, 2023

Summary

NIFI-11905

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using mvn clean install -P contrib-check
    • JDK 17

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

@pvillard31
Copy link
Contributor

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.

@asfgit asfgit closed this in 66fc11d Aug 3, 2023
asfgit pushed a commit that referenced this pull request Aug 3, 2023
Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes #7569.
exceptionfactory pushed a commit to exceptionfactory/nifi that referenced this pull request Aug 14, 2023
Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com>

This closes apache#7569.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants