You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Ruben Q L (Jira)" <ji...@apache.org> on 2026/08/26 09:17:00 UTC

[jira] [Assigned] (CALCITE-7745) Implement a mechanism to restrict the connection properties that can be set by the caller

     [ https://issues.apache.org/jira/browse/CALCITE-7745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruben Q L reassigned CALCITE-7745:
----------------------------------

    Assignee: Ruben Q L

> Implement a mechanism to restrict the connection properties that can be set by the caller
> -----------------------------------------------------------------------------------------
>
>                 Key: CALCITE-7745
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7745
>             Project: Calcite
>          Issue Type: Improvement
>          Components: avatica
>            Reporter: Ruben Q L
>            Assignee: Ruben Q L
>            Priority: Major
>             Fix For: avatica-1.29
>
>
> In Avatica, an authenticated caller can set any Avatica connection property (that is not restricted by the server's configuration), see JdbcMeta#openConnection.
> However, at the moment, there's no mechanism to implement such restriction, so it needs to be implemented (e.g. via allowlist/denylist, similar to Calcite's system properties "calcite.model.classes.allowed" & "calcite.model.classes.denied").
> For backwards compatibility, the default of this new mechanism should probably be "everything is allowed".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)