[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266909#comment-15266909
]
ASF GitHub Bot commented on FLINK-3793:
---------------------------------------
Github user vasia commented on a diff in the pull request:
https://github.com/apache/flink/pull/1955#discussion_r61761448
--- Diff: docs/apis/table.md ---
@@ -57,6 +52,170 @@ The following dependency must be added to your project
in order to use the Table
Note that the Table API is currently not part of the binary distribution.
See linking with it for cluster execution [here]({{ site.baseurl
}}/apis/cluster_execution.html#linking-with-modules-not-contained-in-the-binary-distribution).
+
+Registering and Accessing Tables
--- End diff --
I put this here since this is common to both Table API and SQL. Do you mean
having a "Registering Tables" section both under Table API and under SQL?
> Re-organize the Table API and SQL docs
> --------------------------------------
>
> Key: FLINK-3793
> URL: https://issues.apache.org/jira/browse/FLINK-3793
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Table API
> Affects Versions: 1.1.0
> Reporter: Vasia Kalavri
> Assignee: Vasia Kalavri
>
> Now that we have added SQL and soon streaming SQL support, we need to
> reorganize the Table API documentation.
> - The current guide is under "apis/batch/libs". We should either split it
> into a streaming and a batch part or move it to under "apis". The second
> option might be preferable, as the batch and stream APIs have a lot in common.
> - The current guide has separate sections for Java and Scala APIs. These can
> be merged and organized with tabs, like other parts of the docs.
> - Mentions of "Table API" can be renamed to "Table API and SQL", e.g. in the
> software stack figure and homepage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
