Hey! Some questions / comments:
1. Instead of having to implement a method in the interface could we instead use an empty marker interface such as "WithAsyncStateAccess" 2. If a function is marked async can the user use the sync methods of the new v2 state api (v2State.value()), will this still work? What is the performance implication? 3. Why do we need both a sync and async version of the reducer/min/max logic? Could they always use the new async interface? What is the performance implication? Thanks! Gyula On Wed, Dec 4, 2024 at 1:33 PM Zakelly Lan <zakelly....@gmail.com> wrote: > Hi everyone, > > I'd like to start a discussion on FLIP-488: Expose Async State Processing > and New State APIs in Datastream(V1) APIs[1]. > > This FLIP allows Datastream users to leverage the capability of async state > query and disaggregated state management introduced in FLIP-423[2] and its > sub-FLIPs. > > Looking forward to hearing from you! > > [1] https://cwiki.apache.org/confluence/x/yIrREw > [2] https://cwiki.apache.org/confluence/x/R4p3EQ > > > Best, > Zakelly >
