[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268404#comment-15268404 ] ASF GitHub Bot commented on FLINK-3793: --- Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/1955 > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15268328#comment-15268328 ] ASF GitHub Bot commented on FLINK-3793: --- Github user vasia commented on the pull request: https://github.com/apache/flink/pull/1955#issuecomment-216463342 Updated and merging. > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266918#comment-15266918
]
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_r61762758
--- 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 --
> 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266915#comment-15266915
]
ASF GitHub Bot commented on FLINK-3793:
---
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/1955#discussion_r61762024
--- 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 --
No, I mean we should move the subsection about accessing tables to the
respective sections and rename this section to "Registering Tables".
> 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266821#comment-15266821 ] ASF GitHub Bot commented on FLINK-3793: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/1955#issuecomment-216270394 Thanks for the quick update. A few minor suggestions, otherwise good to merge. > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266816#comment-15266816
]
ASF GitHub Bot commented on FLINK-3793:
---
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/1955#discussion_r61755610
--- 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 --
Rename if we move the access section to the corresponding sections.
> 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266812#comment-15266812
]
ASF GitHub Bot commented on FLINK-3793:
---
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/1955#discussion_r61755531
--- 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
+
+
+`TableEnvironment`s have an internal table catalog to which tables can be
registered with a unique name. After registration, a table can be accessed from
the `TableEnvironment` by its name. Tables can be registered in different ways.
+
+*Note that it is not required to register a `DataSet` or `DataStream` as a
table in a `TableEnvironment` in order to process it with the Table API.*
+
+### Register a DataSet
+
+A `DataSet` is registered as a `Table` in a `BatchTableEnvironment` as
follows:
+
+
+
+{% highlight java %}
+ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
+BatchTableEnvironment tableEnv = TableEnvironment.getTableEnvironment(env);
+
+// register the DataSet cust as table "Customers" with fields derived from
the dataset
+tableEnv.registerDataSet("Customers", cust)
+
+// register the DataSet ord as table "Orders" with fields user, product,
and amount
+tableEnv.registerDataSet("Orders", ord, "user, product, amount");
+{% endhighlight %}
+
+
+
+{% highlight scala %}
+val env = ExecutionEnvironment.getExecutionEnvironment
+val tableEnv = TableEnvironment.getTableEnvironment(env)
+
+// register the DataSet cust as table "Customers" with fields derived from
the dataset
+tableEnv.registerDataSet("Customers", cust)
+
+// register the DataSet ord as table "Orders" with fields user, product,
and amount
+tableEnv.registerDataSet("Orders", ord, 'user, 'product, 'amount)
+{% endhighlight %}
+
+
+
+*Note: DataSet table names are not allowed to follow the
`^_DataSetTable_[0-9]+` pattern, as these are reserved for internal use only.*
+
+### Register a DataStream
+
+A `DataStream` is registered as a `Table` in a `StreamTableEnvironment` as
follows:
+
+
+
+{% highlight java %}
+StreamExecutionEnvironment env =
StreamExecutionEnvironment.getExecutionEnvironment();
+StreamTableEnvironment tableEnv =
TableEnvironment.getTableEnvironment(env);
+
+// register the DataStream cust as table "Customers" with fields derived
from the datastream
+tableEnv.registerDataStream("Customers", cust)
+
+// register the DataStream ord as table "Orders" with fields user,
product, and amount
+tableEnv.registerDataStream("Orders", ord, "user, product, amount");
+{% endhighlight %}
+
+
+
+{% highlight scala %}
+val env = StreamExecutionEnvironment.getExecutionEnvironment
+val tableEnv = TableEnvironment.getTableEnvironment(env)
+
+// register the DataStream cust as table "Customers" with fields derived
from the datastream
+tableEnv.registerDataStream("Customers", cust)
+
+// register the DataStream ord as table "Orders" with fields user,
product, and amount
+tableEnv.registerDataStream("Orders", ord, 'user, 'product, 'amount)
+{% endhighlight %}
+
+
+
+*Note: DataStream table names are not allowed to follow the
`^_DataStreamTable_[0-9]+` pattern, as these are reserved for internal use
only.*
+
+### Register a Table
+
+A `Table` that originates from a Table API operation or a SQL query is
registered in a `TableEnvironemnt` as follows:
+
+
+
+{% highlight java %}
+// works for StreamExecutionEnvironment identically
+ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
+BatchTableEnvironment tableEnv = TableEnvironment.getTableEnvironment(env);
+
+// convert a DataSet into a Table
+Table custT = tableEnv
+ .toTable(custDs, "name, zipcode")
+ .where("zipcode = '12345'")
+ .select("name")
+
+// register the Table custT as table "custNames"
+tableEnv.registerTable("custNames", custT)
+{% endhighlight %}
+
+
+
+{% highlight scala %}
+// works for StreamExecutionEnvironment identically
+val env = ExecutionEnvironment.getExecutionEnvironment
+val tableEnv = TableEnvironment.getTableEnvironment(env)
+
+// convert a DataSet into a Table
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266803#comment-15266803 ] ASF GitHub Bot commented on FLINK-3793: --- Github user fhueske commented on a diff in the pull request: https://github.com/apache/flink/pull/1955#discussion_r61755204 --- Diff: docs/apis/table.md --- @@ -33,10 +28,10 @@ under the License. **Table API and SQL are experimental features** -The Table API is a SQL-like expression language that can be embedded in Flink's DataSet and DataStream APIs (Java and Scala). -A `DataSet` or `DataStream` can be converted into a relational `Table` abstraction. You can apply relational operators such as selection, aggregation, and joins on `Table`s or query them with regular SQL queries. -When a `Table` is converted back into a `DataSet` or `DataStream`, the logical plan, which was defined by relational operators and SQL queries, is optimized using [Apache Calcite](https://calcite.apache.org/) -and transformed into a `DataSet` or `DataStream` execution plan. +The Table API is a SQL-like expression language for relational stream and batch processing that can be easily embedded in Flink's DataSet and DataStream APIs (Java and Scala). +The Table API operates on a relational `Table` abstraction, which can be created from external data sources, or existing DataSets and DataStreams. With the Table API, you can apply relational operators such as selection, aggregation, and joins on `Table`s. --- End diff -- "The Table API *and SQL interface* operates..." > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266743#comment-15266743 ] ASF GitHub Bot commented on FLINK-3793: --- Github user vasia commented on the pull request: https://github.com/apache/flink/pull/1955#issuecomment-216260839 Looks any better now? :) > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266550#comment-15266550 ] ASF GitHub Bot commented on FLINK-3793: --- Github user vasia commented on the pull request: https://github.com/apache/flink/pull/1955#issuecomment-216227231 - Thanks for spotting the leftover menu. It's easy to remove. - I'll add orderBy in the operators table - I'll add a note to the SQL section regarding unsupported operations - I like your suggestions. I'll see what I can do :) > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[ https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266498#comment-15266498 ] ASF GitHub Bot commented on FLINK-3793: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/1955#issuecomment-216221749 Thanks for this PR @vasia. I noticed a few things: - The docs page (`./apis/table.html`) still has the menu of the DataSet API on the left hand side. Is it possible to remove it? - Could you add support of `Table.orderBy()` to the table. We forgot to update the docs when the feature was added. - I think we should add a note to the SQL section that it is not feature complete and only supports what the Table API supports. Hence it does not support: Outer joins, distinct aggregates, date and decimal data types, and more . I have a few more suggestions: - Overall, the documentation is quite focused on the Table API and how it integrates with the DataSet and DataStream API. I think it would be good to describe it as an independent API for relational stream *and* batch processing with a good integration into the DataSet and DataStream API. Table API and SQL should be described as equivalent APIs. - We could move the section about table registration out of the Table API section. It is also valid for SQL and could go into the "Using the Table API and SQL" section (or become a top-level section itself). We could also describe the registration as the default way to create tables and the describe the `DataSet`/`DataStream` -> `Table` conversions of the Table API as shortcuts. Might be easier to understand. What do you think? > 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)
[jira] [Commented] (FLINK-3793) Re-organize the Table API and SQL docs
[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15266308#comment-15266308
]
ASF GitHub Bot commented on FLINK-3793:
---
GitHub user vasia opened a pull request:
https://github.com/apache/flink/pull/1955
[FLINK-3793][docs] re-organize table API and SQL docs
- [X] General
- The pull request references the related JIRA issue ("[FLINK-XXX] Jira
title text")
- The pull request addresses only one issue
- Each commit in the PR has a meaningful commit message (including the
JIRA id)
- [X] Documentation
- Documentation has been added for new functionality
- Old documentation affected by the pull request has been updated
- JavaDoc for public methods has been added
- [ ] Tests & Build
- Functionality added by the pull request is covered by tests
- `mvn clean verify` has been executed successfully locally or a Travis
build has passed
- The Table API and SQL guide has been moved to docs/apis and old pages
redirect to the new location.
- The separate Java and Scala guides have been merged with the tab format.
- The Flink stack figure has been updated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vasia/flink table-docs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1955.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1955
commit 79be777b2ed412f39ad5d7f090138a76aa023466
Author: vasia
Date: 2016-05-02T09:00:58Z
[FLINK-3793][docs] re-organize table API and SQL docs
> 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)
