[jira] [Created] (FLINK-22947) Reduce DataSet visibility in documentation

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-22947) Reduce DataSet visibility in documentation

Shang Yuanchun (Jira)
Seth Wiesman created FLINK-22947:
------------------------------------

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