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
Is your feature request related to a problem?
When using the ODBC driver to connect to a Serverless SQL instance, the driver fails to connect. This is because Serverless has a restricted API set, including removing several of the status APIs that the driver uses to test for API health. We already have example implementations for both SQL CLI and SQL JDBC that skip these checks in a serverless environment.
What solution would you like?
When a serverless link is provided instead of a standard cluster link, the driver should skip calling status endpoints on serverless so it can connect correctly.
What alternatives have you considered?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered:
@Swiddis , related to the solutions for SQLCLI and JDBC, these appear to detect SQL Serverless by parsing the URL. I think we should add a specific config option to use Serverless as well (maybe auto-detect by default). Relying on using URL-parsing exclusively might miss some cases (for example using a proxy, or perhaps the user created an alias for the AWS host).
Is your feature request related to a problem?
When using the ODBC driver to connect to a Serverless SQL instance, the driver fails to connect. This is because Serverless has a restricted API set, including removing several of the status APIs that the driver uses to test for API health. We already have example implementations for both SQL CLI and SQL JDBC that skip these checks in a serverless environment.
What solution would you like?
When a serverless link is provided instead of a standard cluster link, the driver should skip calling status endpoints on serverless so it can connect correctly.
What alternatives have you considered?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: