[
https://issues.apache.org/jira/browse/FLINK-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
