[
https://issues.apache.org/jira/browse/FLINK-12417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834597#comment-16834597
]
Timo Walther commented on FLINK-12417:
--------------------------------------
I'm fine with this change as long as it simplifies the overall architecture. We
could still provide a built-in {{ReadOnlyCatalog}} that extends from the
unified class ({{TableCatalog}} or just {{Catalog}}?) and allows users to
simply implement a read-only catalog.
> Merge ReadableCatalog and ReadableWritableCatalog
> -------------------------------------------------
>
> Key: FLINK-12417
> URL: https://issues.apache.org/jira/browse/FLINK-12417
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / API
> Reporter: Bowen Li
> Assignee: Bowen Li
> Priority: Major
> Fix For: 1.9.0
>
>
> As discussed with [~dawidwys], the original purpose to separate
> ReadableCatalog and ReadableWritableCatalog is to isolate access to metadata.
> However, we believe access control and authorization is orthogonal to design
> of catalog APIs and should be of a different effort.
> Thus, we propose to merge ReadableCatalog and ReadableWritableCatalog to
> simplify the design.
> cc [~twalthr] [~xuefuz]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)