Re: Timed out patterns handling using MATCH_RECOGNIZE

Is there a better way? I'm am idealist with regard to streaming SQL semantics, and I'm going to make the 'slippery slope' argument that if we add a TIMEOUT parameter to MATCH_RECOGNIZE, won't we also need to add it to GROUP BY and JOIN? (Because those are also "blocking" operators.) Maybe JOIN

Re: Towards a spec for robust streaming SQL, Part 2

Tyler, Thanks for this. I am reading the document thoroughly and will give my feedback in a day or two. Julian > On Jul 25, 2017, at 12:54 PM, Pramod Immaneni wrote: > > Thanks for the invitation Tyler. I am sure folks who worked on the calcite > integration and

Flink kicks off Calcite integration

First of all, apologies for cross-posting. If you reply, please remove dev@flink and reply to dev@calcite only. Calcite contributors, Fabian Hueske has sent an email to dev@flink [1] on their plans to add SQL and streaming SQL support to Flink using Calcite, and also included a design document