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

He Qi updated FLINK-38848:
--------------------------
    Description: 
For custom catalogs that have access control, read and write permissions can be 
different. However, currently Flink always call {{Catalog#getTable}} to look up 
the table, no matter it's for read or write.

This PR adds a variant of get{{{}Table{}}} that indicates the required write 
privileges. All the write commands will call this new method to look up tables 
instead. This new method has a default implementation that just calls 
get{{{}Table{}}}, so there is no breaking change.

  was:
For custom catalogs that have access control, read and write permissions can be 
different. However, currently Flink always call {{Catalog#getTable}} to look up 
the table, no matter it's for read or write.

This PR adds a variant of {{loadTable}} that indicates the required write 
privileges. All the write commands will call this new method to look up tables 
instead. This new method has a default implementation that just calls 
{{{}loadTable{}}}, so there is no breaking change.


> Catalog#getTable should indicate if it's for writing
> ----------------------------------------------------
>
>                 Key: FLINK-38848
>                 URL: https://issues.apache.org/jira/browse/FLINK-38848
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / Core
>    Affects Versions: 2.1.0
>            Reporter: He Qi
>            Priority: Major
>
> For custom catalogs that have access control, read and write permissions can 
> be different. However, currently Flink always call {{Catalog#getTable}} to 
> look up the table, no matter it's for read or write.
> This PR adds a variant of get{{{}Table{}}} that indicates the required write 
> privileges. All the write commands will call this new method to look up 
> tables instead. This new method has a default implementation that just calls 
> get{{{}Table{}}}, so there is no breaking change.



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

Reply via email to