Releases: forcedotcom/Salesforce-CDP-jdbc
release_2021.9B
Changes:
- Upgrade OkHttp version to 4.8.1
- Log the retry count
- Add support to disable socksProxy. Setting
disableSocksProxy
totrue
would bypass the socks proxy. This could be useful to user who have specified the socks proxy settings as part of Global configuration (via system properties) - Add initial support to v2 API [beta]
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.9A
Changes:
- Add retry few more Http status code (rate limiter exception, Internal Server Error)
- Add retry for Token exchange failures
- Verify credentials during connection creation
- Fail connection creation when specified URL doesn't match existing environments
- Reuse Http Client
- Improve Error propagation to clients
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.7C
7c Release
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.7B
Release PR for 7B
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.7A
Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.6A
Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.5A
Release Notes:
Security issue fix
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.4B
Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.3B
Release notes:
Merge pull request #4 from forcedotcom/develop
Merging develop into master
NOTE: Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.
release_2021.3A
Files were removed out of an abundance of caution due to log4j. While we do not believe log4j was ever an issue with these files, we have removed them to mitigate any potential risk.