hqbhoho commented on issue #7469: URL: https://github.com/apache/gravitino/issues/7469#issuecomment-3026846354
> That's ok, but as far as I know, Trino only accepts configuration keys that are explicitly defined. The revised version might not be valid under that constraint. @diqiu50 Thank you for feedback! `trino.bypass.direct.xxxxx` may require user to ensure the correctness of the configuration themselves. If a configuration is not recognized by Trino, it should prevent the creation of the catalog. Since new versions of Trino may introduce new configurations, this parameter effectively reduces coupling issues. Otherwise, each time we adapt to a new version of Trino, we would need to account for any changes in the configuration. We have made secondary developments to Trino with some independent configurations. However, when using Gravitino, we found that our custom configurations are not taking effect. I will file a PR to support `trino.bypass.direct.xxxxx`. -- 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]
