[jira] [Commented] (FLINK-12395) Reconcile description and detailed description in CatalogBaseTable

["Dawid Wysakowicz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-12395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832346#comment-16832346 ] 

Dawid Wysakowicz commented on FLINK-12395:
------------------------------------------

Hi [~phoenixjiangnan]
I believe it is not equivalent to a comment. I think the idea was to use it for a {{DESCRIBE}} command. In this context it makes sense to have both {{getDescritpion()}} and {{getDetailedDescription()}} as many catalogs already differentiate that as well, e.g. hive has {{DESCRIBE}} and {{DESCRIBE EXTENDED}} https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Describe

> 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)