Re: [DISCUSS] Towards Calcite 1.18

2018-10-21 Thread Michael Mior
Thanks for continuing to push releases forward! Unfortunately I won't be able to volunteer to be release manager this time around, but I'll try to set aside some time to go through some PRs. On Sat, Oct 20, 2018, 02:21 Julian Hyde wrote: > OK, it's now exactly 3 months since 1.17. I think it's t

Calcite on Traces / Industry 4.0 data

2018-10-21 Thread Julian Feinauer
Dear calcite devs, I follow the project for a long time and love how calcite made it possible to use SQL everywhere (have done several sql interfaces on top of specific file formats myself). I also like the strong support for streaming SQL. The reason I'm writing this email is not only to give

Re: Calcite on Traces / Industry 4.0 data

2018-10-21 Thread Mark Hammond
Hi Julian Feinauer, Do share your thoughts on MATCH_RECOGNIZE operator suitability, http://mail-archives.apache.org/mod_mbox/calcite-dev/201807.mbox/%3cc6a37dae-f884-4d90-8ec0-8fd4efde1...@apache.org%3e Cheers, Mark. > On 22 Oct 2018, at 02:24, Julian Feinauer > wrote: > > Dear calcite devs,

Re: Calcite on Traces / Industry 4.0 data

2018-10-21 Thread Julian Feinauer
Hi Mark, thanks for your reply. In fact, I'm sorry that I missed to mention MATCH_RECOGNIZE in my original mail. I was really excited when I first heard about MATCH_RECOGNIZE as it is incredibly powerful and could be used so solve many of the problems I state in my mail. The only "drawback" I se