Hi all,
sorry for joining late. Looking at the target structure of our
documentation as discussed in FLIP-42 [1] we will have some sections, which
cover both APIs (SQL/Table and DataStream). These include
* Getting Started
* Concepts
* Deployments
* Operations
* Connectors
* Libraries (CEP, ML)
Hi all,
thanks for your feedback.
@Stephan: Our efforts will definitely be synced with the general Flink
documentation improvements mentioned in FLIP-42. I also had an offline
discussion with Konstantin about this. Concepts such as streaming
concepts, time, order, etc. should definitely
>>> Should the table API concepts be a section in the overall concepts then?
I would say yes, but not exactly as table API concept, but for streaming SQL
concept, plus how to unify the streaming and batch from SQL's perspective.
This topic has lots of connection with underlying streaming
There are also some other efforts to restructure the docs, which have
resulted until now in more quickstarts and more concepts.
IIRC there is the goal to have a big section on concepts for the whole
system: streaming concepts, time, order, etc.
The API docs would be really more about an API
big +1 to the idea of restructuring the docs. We got a lot of complaints
from users about the Table & SQL docs.
In general, I think the new structure is very nice.
Regarding to moving "User-defined Extensions" to corresponding broader
topics, I would prefer current "User-defined Extensions".
+1 to the general idea and thanks for driving this. I think the new
structure is
more clear than the old one, and i have some suggestions:
1. How about adding a "Architecture & Internals" chapter? This can help
developers
or users who want to contribute more to have a better understanding about
Agree with Dawid's suggestion about function.
Having a Functions section to unify the built-in function and UDF would be
better.
Dawid Wysakowicz 于2019年8月30日周五 下午7:43写道：
> +1 to the idea of restructuring the docs.
>
> My only suggestion to consider is how about moving the
>
+1 to the idea of restructuring the docs.
My only suggestion to consider is how about moving the
User-Defined-Extensions subpages to corresponding broader topics?
Sources & Sinks >> Connect to external systems
Catalogs >> Connect to external systems
and then have a Functions sections with
Hi everyone,
the Table API & SQL documentation was already in a very good shape in
Flink 1.8. However, in the past it was mostly presented as an addition
to DataStream API. As the Table and SQL world is growing quickly,
stabilizes in its concepts, and is considered as another top-level API
