[
https://issues.apache.org/jira/browse/FLINK-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944049#comment-15944049
]
Fabian Hueske commented on FLINK-5829:
--------------------------------------
I just had a chat with [~wheat9] and we came to the conclusion that using a
custom schema is not so easy. We could register a sub-schema, but then all
table references in SQL queries would need to be prefixed with the schema name.
In fact, I'm not sure how important it is to be able to remove tables from the
root schema. It seems that this would be mostly relevant for long running
applications that run many queries. Such applications could also register an
own external catalog and manage the available tables themselves.
What do you think, @twalthr?
> Bump Calcite version to 1.12 once available
> -------------------------------------------
>
> Key: FLINK-5829
> URL: https://issues.apache.org/jira/browse/FLINK-5829
> Project: Flink
> Issue Type: Task
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: Haohui Mai
>
> Once Calcite 1.12 is release we should update to remove some copied classes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
