+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 <rmetz...@apache.org> wrote: > Thank you Fabian for working on the proposal. > > On Thu, May 18, 2017 at 3:51 PM, Fabian Hueske <fhue...@gmail.com> 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 the docs, but it won't be trivial to do > > this, IMO because there are many orthogonal aspects: > > - Stream/Batch > > - Table/SQL > > - Scala/Java > > > > and sometimes also common concepts. > > At the moment there are also many new features missing like OVER windows, > > UDAGGs, retraction, StreamTableSinks, time indicator attributes, filter > > pushdown, ... > > > > I will try to sketch a new structure in a Google Doc in the next days and > > share it in this thread. > > > > Cheers, Fabian > > > > 2017-05-18 14:03 GMT+02:00 Kostas Kloudas <k.klou...@data-artisans.com>: > > > > > A big +1 as well. > > > > > > > On May 18, 2017, at 1:55 PM, Ufuk Celebi <u...@apache.org> wrote: > > > > > > > > On Thu, May 18, 2017 at 1:52 PM, Till Rohrmann <trohrm...@apache.org > > > > > 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 > > > > > > > > >
