-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Add an extras
field for Presto connection
#3909
Conversation
Did you know that we have a Qubole query runner? |
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of your project's GitHub integration settings. You can manage this integration in your project's settings in the Cypress Dashboard |
Oops, didn't see that... But can this PR be of any use for other scenarios still? |
This is mostly for allowing self-assigned SSL certificate. For example, services like [Qubole](https://docs.qubole.com/en/latest/user-guide/presto/connect-to-presto-when-ssl-enabled.html) only allows SSL connection via self-assigned CA certificate. The default value (placeholder) should have made it obvious what this field is for for those who need it.
In lower version of Presto, sometimes the old query will throw "outputFormat should not be accessed from a null StorageFormat" error (see prestodb/presto#6972).
This makes it possible to allow arbitrary connection parameters that are not stored as configuration field. Also extended Dynamic Forms to allow JSON validation.
This makes it possible to allow arbitrary connection parameters that are not stored as configuration field. Also extended Dynamic Forms to allow JSON validation.
This makes it possible to allow arbitrary connection parameters that are not stored as configuration field. Also extended Dynamic Forms to allow JSON validation.
What type of PR is this? (check all applicable)
Description
This added a new "Extras" fields for Presto connection,
mostly for allowing self-assigned SSL certificate.
For example, services like Qubole
only allows SSL connection via self-assigned CA certificate.
Example usage is to include
requests_kwargs
as JSON string:Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings (if there are UI changes)