You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2020/02/18 14:26:00 UTC

[jira] [Commented] (FLINK-16146) Improve end-to-end usability of Flink Table API & SQL

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

Dawid Wysakowicz commented on FLINK-16146:
------------------------------------------

I might be nitpicking here, but I doubt this issue is useful.

As I understand issues should have a defined scope. As I see this issue it will never end. You can always come up with ways to improve user experience.  Moreover it limits the nesting possibility for sub-tasks of this issue. JIRA does not allow you to have arbitrary nesting. 

If we need a way to group those kind of issues. Probably for searching (my guess that was the purpose of this issue), I would prefer creating a separate label. Or just reusing the existing one. (Component: Table SQL /* + label: usability)

> Improve end-to-end usability of Flink Table API & SQL
> -----------------------------------------------------
>
>                 Key: FLINK-16146
>                 URL: https://issues.apache.org/jira/browse/FLINK-16146
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Common, Table SQL / API, Table SQL / Client
>            Reporter: Jark Wu
>            Priority: Major
>              Labels: usability
>
> This is an umbrella issue to track the usability problems in the end-to-end experience of Flink Table API & SQL. This may include API improvements or connectors improvements.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)