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 <wshaox...@gmail.com> wrote: > 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/UDAGG/window aggregate, etc. > If this sounds good to you, I can help to refactor the pages. > > Regards, > Shaoxuan > > > On Thu, May 18, 2017 at 5:01 PM, Robert Metzger <rmetz...@apache.org> > wrote: > > > 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 this change as part of the documentation > > writing of the new 1.3 features. > > > > Let me know what you think. > > > > > > Regards, > > Robert > > >
