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

Upgrade Databricks JDBC driver to 2.6.29 #14465

Closed
wants to merge 3 commits into from
Closed

Conversation

ebyhr
Copy link
Member

@ebyhr ebyhr commented Oct 5, 2022

Description

Testing if new JDBC driver resolves #14391
Download Databricks JDBC driver release-notes

Non-technical explanation

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Oct 5, 2022
@ebyhr ebyhr force-pushed the ebi/delta-databricks-jdbc branch from 9672208 to bf12807 Compare October 5, 2022 09:16
@ebyhr
Copy link
Member Author

ebyhr commented Oct 5, 2022

Closing as upgrading the JDBC driver didn't help.

tests               | 2022-10-05 23:15:58 INFO: FAILURE     /    io.trino.tests.product.deltalake.TestDeltaLakeTransactionLogCache.testAllDataFilesAreLoadedWhenTransactionLogFileAfterTheCachedTableVersionIsMissing (Groups: profile_specific_tests, delta-lake-databricks, delta-lake-oss) took 11.7 seconds
tests               | 2022-10-05 23:15:58 SEVERE: Failure cause:
tests               | io.trino.tempto.query.QueryExecutionException: java.sql.SQLException: [Databricks][DatabricksJDBCDriver](500593) Communication link failure. Failed to connect to server. Reason: HTTP retry after response received with no Retry-After header, error: HTTP Response code: 503, Error message: Unknown.

@ebyhr ebyhr closed this Oct 5, 2022
@ebyhr ebyhr deleted the ebi/delta-databricks-jdbc branch October 5, 2022 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Flaky "Communication link failure" in Databricks tests
1 participant