dominikhei opened a new pull request, #53134: URL: https://github.com/apache/airflow/pull/53134
--- I haven't really found a standard way of how multiple auth types in connection are handled, but the Trino provider currently has some opaque behavior, is there an explanation why it is done this way? currently: - password and jwt auth can be set at the same time, but password will be preferred - password and kerberos can't - password and cert can't - jwt and kerberos or cert can, but jwt will be preferred - kerberos and cert can, but kerberos will be preferred I've simplified the logic so that only one authentication method may be specified per connection. If multiple are provided, an error is raised. This avoids silent misconfigurations and makes the behavior explicit and predictable. If someone thinks, that this is a bad idea and can explain me the rationale behind the current logic, please let me know :) Question: Could this change be considered a bugfix? I’m hesitant to introduce a breaking change for this issue. If this is considered breaking, I would prefer enhancing logging instead, to clearly inform users which authentication type is actually used -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
