Hi, 1. I think those changes will mostly bring new features/functionalities to the existing Streaming APIs in order to fully support batch executions. For example one way or another to better handle "bounded data streams" in the DataStream API. 2. I think there is and there is not going to be one single umbrella ticket, as this whole idea is going to take quite a bit of time to fully design. There are a couple of the initial design proposals connected with the batch and streaming unification: FLIP-134 [1] FLIP-147 [2] But I'm pretty sure more will follow in the future.
Best, Piotrek [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-134%3A+Batch+execution+for+the+DataStream+API [2] https://cwiki.apache.org/confluence/display/FLINK/FLIP-147%3A+Support+Checkpoints+After+Tasks+Finished śr., 6 sty 2021 o 16:20 burkaygur <burkay...@gmail.com> napisał(a): > Hi Flink Community, > > Really excited for the "true unification" of Batch and Stream APIs, and had > a few questions for clarification after reading the release notes, and > watching the video by aljoscha here > <https://www.youtube.com/watch?v=z9ye4jzp4DQ> . > > > 1) How do these changes impact the Table and SQL APIs? Are they completely > orthogonal or can we get the benefits of the new Batch Mode with Flink SQL > as well? > 2) What is the best ticket to follow the roadmap & track the progress of > this whole project. Specifically the parts about bootstrapping of state. I > would love to help contribute to it. > > Best, > Burkay > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
