You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/05/14 17:38:00 UTC

[jira] [Closed] (FLINK-12469) Clean up catalog API on default/current DB

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

Bowen Li closed FLINK-12469.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

merged in 1.9.0:  1c3ac2f82b707ae12556a5883980da8050510244

> Clean up catalog API on default/current DB
> ------------------------------------------
>
>                 Key: FLINK-12469
>                 URL: https://issues.apache.org/jira/browse/FLINK-12469
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: Xuefu Zhang
>            Assignee: Xuefu Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently catalog API has get/setCurrentDatabase(), which is more user session specific. In our design principal, catalog instance is agnostic to user sessions. Thus, current database concept doesn't belong there. However, a catalog should support a (configurable) default database, which would be taken as user's current database when user's session doesn't specify a current DB.
> This JIRA is to remove current database concept from catalog api and add default database instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)