SNOW-987122 Upgrade JDBC to 3.14.5 and Catch new exception type for r…

[sfc-gh-japatel]

…enewing expired S3 token

Changes

• Here is the reason why we were not able to run for more than 1 hour when updating JDBC to latest available version: https://github.com/snowflakedb/snowflake-jdbc/pull/1473/files

• @sfc-gh-lsembera did add a retry logic but that only compatible with version 3.13.30

• Few changes are because of formatter.

• isCredentialsExpiredException function is removed!

  • we will retry on all exceptions and run metadata refresh on first exception.

• Fixed a failing test and will fix it once next version of JDBC is released: https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/819

  • The issue is only while JDBC query reads a column containing large values, not writing to table.

• Ran longRunningTest present in E2E Jar. Look at this commit's E2E runs: (Took> 2 hours to run) 35c8468029dcdbd243bf2e73710833798ceb8f68

[sfc-gh-xhuang]

can close https://github.com/snowflakedb/snowflake-ingest-java/pull/660

[sfc-gh-psaha]

I expect large values test to fail until SNOW-1003775 is fixed but you can work around by changing the tests to read back the length of values instead of the values themselves. Note that gh actions will just crash for these failures and you won't see a proper test failure in the logs. @sfc-gh-japatel

[sfc-gh-japatel]

I expect large values test to fail until SNOW-1003775 is fixed but you can work around by changing the tests to read back the length of values instead of the values themselves. Note that gh actions will just crash for these failures and you won't see a proper test failure in the logs. @sfc-gh-japatel

Ahh yes, thats what I am seeing, FlushServiceTests are running indefinitely and no errors as well! Thanks for pointing it out

[sfc-gh-japatel]

Snyk checks can be ignored since it is complaining pom of e2e library

[sfc-gh-tzhang]

Snyk checks can be ignored since it is complaining pom of e2e library

I don't think this can be ignored since we don't see this issue before, and I assume Snyk will keep failing and we will miss real issues if it keeps like this

[sfc-gh-xhuang]

Snyk checks can be ignored since it is complaining pom of e2e library

I don't think this can be ignored since we don't see this issue before, and I assume Snyk will keep failing and we will miss real issues if it keeps like this

I had already created an jira last week and assigned to @sfc-gh-jfan to help investigate. SNOW-1045928

[sfc-gh-japatel]

Folks, updated the PR with:

1. Kept using jdbc 3.13.5, modify test
2. No special exception handling, catch all exception and retry on very first exception.

Thanks, PTAL!