Here is the biggest recent thread on this. You might also ask directly what they think about the algebraic issue as you see it.
https://mail-archives.apache.org/mod_mbox/flink-dev/201506.mbox/%3CCANMXwW3bOgaJhG_syH2%3D0x5BcdukyTOF0dU3dM4_3yQK2UHoyw%40mail.gmail.com%3E Here are some thoughts that mostly deal with implementation, but also discuss a few theoretical aspects. These then link into concepts such as data types (Flink recognized sortedness in type information, for instance), the snaphost algorithms (because window triggers are very similar to the Lamport/Chandry algorithms used for snapshots and state handling), the optimizer (only a side comment in this regard) and other aspects. https://docs.google.com/document/d/1rSoHyhUhm2IE30o5tkR8GEetjFvMRMNxvsCfoPsW6_4/edit#heading=h.faju7vv5ilgm On Sun, Jun 28, 2015 at 12:48 AM, Julian Hyde <[email protected]> wrote: > Ted, > > Do you have a link to a pertinent email thread from the Flink list? > > I can see how shifting from monotonic to k-sorted or punctuation could > make a big impact to the runtime of a streaming system like Flink. But I > don’t think the impact on the algebra is as big, and that’s what we’re > concerned with in Calcite. > > Julian > > > > On Jun 26, 2015, at 11:18 PM, Ted Dunning <[email protected]> wrote: > > > > On Sat, Jun 27, 2015 at 1:13 AM, Julian Hyde <[email protected]> wrote: > > > >> Algebraic reasoning based on monotonicity can be extended to the other > >> models. If we start with the more complex models we'd soon we up to > >> our hubcaps in theoretical mud. > >> > > > > As you like. Flink has just had to rip up and repair a bunch of stuff > > precisely because they started with an assumption of monotonicity and had > > to move to a looser model. The practical impact was pretty substantial > and > > substantially larger than the comments here would imply. > >
