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

Support for custom JDBC Connection properties #73

Open
anandp504 opened this issue Nov 5, 2015 · 1 comment
Open

Support for custom JDBC Connection properties #73

anandp504 opened this issue Nov 5, 2015 · 1 comment

Comments

@anandp504
Copy link

We use play-hikaricp plugin to pool database connection with Vertica. Vertica supports automatic switchover to one of the nodes in the cluster if the primary node goes down through the jdbc property BackupServerNode. However, play-hikaricp plugin doesn't seem to honour the custom connection property and hence we are not able to fallback to a different node in the cluster if the node mentioned in db.default.url property goes down. Is there a way to make this property work with HikariCP? We have verified that if we actually create a java.util.Properties and use that to create a JDBC Connection using HikariCP, it works.

db.default.url="jdbc://postgresql://IP-Address:Port/DBName"
db.default.BackupServerNode="node2-domain,node3-domain"

@marcospereira
Copy link
Contributor

Hello @anandp504,

Problem here is that we are mapping properties individually and in a very specific way, as you can see in the code bellow:

https://github.com/edulify/play-hikaricp.edulify.com/blob/master/app/com/edulify/play/hikaricp/HikariCPConfig.scala

Could you please post the code you mentioned that works as expected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants