[
https://issues.apache.org/jira/browse/FLINK-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250542#comment-15250542
]
ASF GitHub Bot commented on FLINK-3727:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/1917#discussion_r60471750
--- Diff: docs/apis/batch/libs/table.md ---
@@ -419,8 +438,8 @@ Only the types `LONG` and `STRING` can be casted to
`DATE` and vice versa. A `LO
SQL
----
The Table API also supports embedded SQL queries.
-In order to use a `Table` or `DataSet` in a SQL query, it has to be
registered in the `TableEnvironment`, using a unique name.
-A registered `Table` can be retrieved back from the `TableEnvironment`
using the `scan()` method:
+In order to use a `Table`, `DataSet`, or `DataStream` in a SQL query, it
has to be registered in the `TableEnvironment`, using a unique name.
+A registered Dataset `Table` can be retrieved back from the
`TableEnvironment` using the `scan()` method:
--- End diff --
Add a sentence about the `ingest()` method.
> Add support for embedded streaming SQL (projection, filter, union)
> ------------------------------------------------------------------
>
> Key: FLINK-3727
> URL: https://issues.apache.org/jira/browse/FLINK-3727
> Project: Flink
> Issue Type: Sub-task
> Components: Table API
> Affects Versions: 1.1.0
> Reporter: Vasia Kalavri
> Assignee: Vasia Kalavri
>
> Similar to the support for SQL embedded in batch Table API programs, this
> issue tracks the support for SQL embedded in stream Table API programs. The
> only currently supported operations on streaming Tables are projection,
> filtering, and union.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
