Hi,
I merged the feature branch back to the master and the release-1.3 branch
and deleted it.
There are still a few gaps in the docs that need to be filled (there are
JIRAs for those), but the overall structure looks good IMO and most aspects
of the APIs are covered.
Cheers, Fabian
2017-05-28 15
Hi everybody,
I added a couple of subissues to
https://issues.apache.org/jira/browse/FLINK-5354 and started to work on the
first two.
I'll open PRs for those soon.
Please pick an issue and assign it to yourself if you want to help with the
Table API / SQL documentation.
Thanks,
Fabian
2017-05-
Hi everybody,
I pushed the branch to the ASF Flink repository as a feature branch to keep
all PRs in one place:
--> https://github.com/apache/flink/tree/tableDocs
Thanks,
Fabian
2017-05-23 16:25 GMT+01:00 Fabian Hueske :
> Hi everybody,
>
> I prepared a branch that creates the proposed struct
Hi everybody,
I prepared a branch that creates the proposed structure and copied the
existing documentation into the corresponding pages / sections.
There are plenty of gaps that need to be filled or reworked.
--> https://github.com/fhueske/flink/tree/tableDocs
How do we go on from here?
I think
Hi everybody,
Thanks for the feedback. I'll go ahead and create the proposed structure
and move the content of the existing docs with comments of what needs to be
adapted.
I'll put this into branch of my Github repo and let you know when I'm done.
>From there, we can distribute working on the miss
Hi, Fabian,
Thanks for the sketch. The structure is pretty well to me, And glad to
join in the discussion in google doc.
Cheers,
SunJincheng
2017-05-19 14:55 GMT+08:00 Shaoxuan Wang :
> Hello Fabian,
> Thanks for drafting the proposal. I like the entire organization in general
> and left a fe
Hello Fabian,
Thanks for drafting the proposal. I like the entire organization in general
and left a few comments. I think this will be a very good kick off to
reorganize the tableAPI&SQL doc.
-shaoxuan
On Fri, May 19, 2017 at 7:06 AM, Fabian Hueske wrote:
> Hi everybody,
>
> I came up with a p
Hi everybody,
I came up with a proposal for the structure of the Table API / SQL
documentation:
https://docs.google.com/document/d/1ENY8tcPadZjoZ4AQ_lRRwWiVpScDkm_4rgxIGWGT5E0/edit?usp=sharing
Feedback and comments are very welcome.
Once we agree on a structure, we can create skeletons and distr
+1
The Table / SQL component has made significant progress in the last few
months (kudos to all contributors).
It is a good time to have a documentation to reflect all the changes in the
Table / SQL side.
On Thu, May 18, 2017 at 8:12 AM Robert Metzger wrote:
> Thank you Fabian for working on
Thank you Fabian for working on the proposal.
On Thu, May 18, 2017 at 3:51 PM, Fabian Hueske wrote:
> Thanks for starting this discussion Robert.
>
> I think with the next release the Table API / SQL should be moved up in the
> Application Development menu.
> I also though about restructuring th
Thanks for starting this discussion Robert.
I think with the next release the Table API / SQL should be moved up in the
Application Development menu.
I also though about restructuring the docs, but it won't be trivial to do
this, IMO because there are many orthogonal aspects:
- Stream/Batch
- Tabl
A big +1 as well.
> On May 18, 2017, at 1:55 PM, Ufuk Celebi wrote:
>
> On Thu, May 18, 2017 at 1:52 PM, Till Rohrmann wrote:
>> I think we have a history of creating too long monolithic documentation
>> pages which are hard to digest. So a big +1 for splitting the Table API/SQL
>> documentatio
On Thu, May 18, 2017 at 1:52 PM, Till Rohrmann wrote:
> I think we have a history of creating too long monolithic documentation
> pages which are hard to digest. So a big +1 for splitting the Table API/SQL
> documentation up into more easily digestible pieces.
+1
Thanks for bringing it up
I think we have a history of creating too long monolithic documentation
pages which are hard to digest. So a big +1 for splitting the Table API/SQL
documentation up into more easily digestible pieces.
Cheers,
Till
On Thu, May 18, 2017 at 12:01 PM, Shaoxuan Wang wrote:
> Hi Robert,
> This sounds
Hi Robert,
This sounds great to me. While I am in the middle of writing-up UDAGG doc
(FLINK-5905), I also feel it's not good to have entire tableAPI&SQL
introduction in one page.
We can move tableAPI&SQL under "application development", and split it into
small sub-topics, such as basic/UDF/UDTF/UDA
Hi,
I'm wondering whether we should make the Table API a bit more prominent in
our documentation by upgrading it from below "Libraries" to the same level
as "DataSet" and "DataStream".
This would also allow us to split it from one large page into smaller
sub-pages.
I think it would be nice to do
16 matches
Mail list logo
