Hubert Łojek

## Description Invoked PTF from a `SECURITY DEFINER` view using `LocalQueryRunner` cause to call incorrect overloaded method `checkCanGrantExecuteFunctionPrivilege`. This cause perform a wrong check from `SystemAccessControl`, this check invoked: ```...

Add checkCanGrantExecuteFunctionPrivilege to ConnectorAccessControl

3

## Description Follow-up to https://github.com/trinodb/trino/pull/13944 I will needed this to complete https://github.com/trinodb/trino/pull/13713 ## Release notes ( ) This is not user-visible and no release notes are required. ( ) Release...

## Description This PR add checks if user has an access to catalog and schema in `USE` statement. ## Related issues, pull requests, and links - Fixes https://github.com/trinodb/trino/issues/14208 ## Non-technical...

## Description This PR filter out values using configured access control from tables: - `analyze_properties` - `column_properties` - `materialized_view_properties` - `schema_properties` - `table_properties` ## Related issues, pull requests, and links...

Add table functions support to File-based access control

4

## Description This PR adds File-based access control support for table functions. Before this PR with File-based access control enabled every table functions was denied. By default every rule kind...

Bug notice by @dedep I have configured File-based Access Control with a rules: ``` { "catalogs": [] } ``` so the only visible catalog should be `system` but using `USE`...

Not all tables from system.metadata are access control aware

2

I notice some tables from `system.metadata` does not respect rules from File-based Access Control, I got the rules: ``` { "catalogs": [], "tables": [{ "catalog": "system", "schema": "metadata", "privileges": [...