-
Notifications
You must be signed in to change notification settings - Fork 31
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
The required connection property does not found ClusterID #54
Comments
Thanks for reporting issue. We will get back to you ASAP. In the mean time if you can generate driver logs that will be helpful to troubleshoot the issue. Please don't use undocumented property. This may be because driver detect serverless end point by looking at host and it should contains "redshift-serverless". Now you use NLB, so it thinks you connect to provision cluster. Need to check with team how to detect incase of NLB. |
Hi Toby, I discuss with team. We are going to expose new connection properties for serverless in case NLB where driver can't get needed information from the URL. So we will expose isServerless, account_id, work_group etc. as new connection properties. I know, you use internal property to work around. But we will expose new set of properties as officially supported. |
Fix in 2.1.0.8 driver release. Check the Readme for download links. |
is this available? We are running into the same issue with serverless redshift & NLB URL in the connection string. None of the workarounds above seem to work. Using 2.1.0.28 |
this doesn't seem to work with redshift serverless fronted by the NLB |
Driver version
2.1.0.7
Redshift version
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.38431
Client Operating System
Windows 10
JAVA/JVM version
11.0.12
Table schema
N/A
Problem description
The standard connection paramaters are incompatible with Serverless clusters when using IAM authentication and connecting via a network load balancer (NLB).
Expected behaviour:
It should be possible to connect with the connection string jdbc:redshift:iam://{nlb-host}:5439/dev?AccessKeyID={xx}&SecretAccessKey={xx}
Actual behaviour:
Error message received
Error message/stack trace:
The required connection property does not found ClusterID
Any other details that can be helpful:
I managed to overcome this issue and successfully connect by adding 'isServerless=true' to the connection string. However, this parameter is not mentioned anywhere in the Redshift docs.
The text was updated successfully, but these errors were encountered: