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

[FEATURE] SQL Serverless support #70

Open
Swiddis opened this issue Oct 28, 2024 · 1 comment
Open

[FEATURE] SQL Serverless support #70

Swiddis opened this issue Oct 28, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Swiddis
Copy link
Collaborator

Swiddis commented Oct 28, 2024

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

@Swiddis Swiddis added enhancement New feature or request untriaged and removed untriaged labels Oct 28, 2024
@jduo
Copy link

jduo commented Nov 1, 2024

@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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants