[
https://issues.apache.org/jira/browse/FLINK-22947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360940#comment-17360940
]
Seth Wiesman commented on FLINK-22947:
--------------------------------------
fixed in master: 3e884f1cfe89e986826d6664fc7faadd48f47388
> Reduce DataSet visibility in documentation
> ------------------------------------------
>
> Key: FLINK-22947
> URL: https://issues.apache.org/jira/browse/FLINK-22947
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
> Reporter: Seth Wiesman
> Assignee: Seth Wiesman
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Now that the legacy planner has been dropped and bounded datastream execution
> has landed, the primary remaining use cases for DataSet are gone however it
> is still featured prominently in our documentation.
>
> In particular, it is listed second under Application Development, below
> DataStream but above table and Python. Additionally, Application Development
> has top-level dropdowns for serialization and managing execution even though
> these sections are only relevant for JVM DataStream and DataSet.
>
> We should
> 1) move dataset to the bottom of the list and add a legacy label
> 2) move serialization to be a subsection of datastream
> 3) evaluate which pages under managing execution are still relevant and see
> if there are more appropriate places to put them.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
