[
https://issues.apache.org/jira/browse/FLINK-12395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832443#comment-16832443
]
Timo Walther commented on FLINK-12395:
--------------------------------------
Yes, this was the intention. The pure {{DESCRIBE}} command can return the
comment section. A {{DESCRIBE EXTENDED}} could return more internal information
such as catalog specifics (location, access grants, etc.). It would be great to
improve the JavaDocs in those classes to understand the difference for other
contributors and implementers.
> Reconcile description and detailed description in CatalogBaseTable
> ------------------------------------------------------------------
>
> Key: FLINK-12395
> URL: https://issues.apache.org/jira/browse/FLINK-12395
> Project: Flink
> Issue Type: Sub-task
> Reporter: Bowen Li
> Priority: Major
> Fix For: 1.9.0
>
>
> CatalogBaseTable has {{getDescritpion()}} and {{getDetailedDescription()}}
> API, which don't seem to make such sense. I'm not sure what's the use case of
> detailed description, and how should users specify it in SQL and table api.
> Probably should remove detailed description and rename "description" to
> "comment".
> Besides, for simplicity, we should consider just treating "comment" as a
> property in properties map.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
