You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
When try to create PRESTO datasource type, if jdbc connect parameters assigned.
TestConnect will be failed with tips "JDBC connect failed".
For example, use {"SSL":"true"} as connect params:
the logs will shows:
[ERROR] 2022-09-01 11:38:21.728 +0800 com.zaxxer.hikari.pool.HikariPool:[594] - HikariPool-2 - Exception during pool initialization.
java.sql.SQLException: Connection property 'SSL' is both in the URL and an argument
What you expected to happen
Because "SSL" is a valid property when connect presto, so the test connect should be success.
How to reproduce
As above.
Two points mentioned:
plz just use jdbc connet params at first to avoid the dataSourceClientCache, bcz cache key does not contain params.
IMO, when connect presto, we can set params either in jdbc-url or properties, However, the same parameter may not be specified using both methods, ref to JDBC driver
I'm pleasure to fix this, and what is next?
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
Search before asking
What happened
When try to create PRESTO datasource type, if jdbc connect parameters assigned.
TestConnect will be failed with tips "JDBC connect failed".
For example, use
![image](https://user-images.githubusercontent.com/2315481/187828629-e44af806-96a9-4923-8e0b-2de73e8d9d8f.png)
{"SSL":"true"}
as connect params:the logs will shows:
What you expected to happen
Because "SSL" is a valid property when connect presto, so the test connect should be success.
How to reproduce
As above.
Two points mentioned:
I'm pleasure to fix this, and what is next?
Anything else
Every time happens.
Version
3.0.0
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: