Thanks Fabian for the standard Row Pattern Recognition in SQL!
I just created a FLIP for this feature.
FILP-20:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-20%3A+Integration+of+SQL+and+CEP
Cheers,
Jark Wu
2017-06-16 0:49 GMT+08:00 Fabian Hueske :
> Hi everybody,
Hi everybody,
I just stumbled over this blog post [1] which discusses new features in SQL
2016.
Apparently the match_recognize clause is part of that. The blogpost also
contains a slide set that presents the pattern matching feature and a link
to a 90 page technical report.
I thought this might
@Jark: You should now have the permissions to create pages in the Flink
wiki.
Cheers,
Till
On Thu, Jun 15, 2017 at 5:11 AM, Jark Wu wrote:
> Hi Till,
>
> Could you grant me the edit permission of Flink WIKI? My id is imjark.
>
> Thanks,
> Jark Wu
>
> 2017-06-15 0:07 GMT+08:00
Hi Till,
Could you grant me the edit permission of Flink WIKI? My id is imjark.
Thanks,
Jark Wu
2017-06-15 0:07 GMT+08:00 Till Rohrmann :
> I think that the integration of SQL and CEP would make a good FLIP.
>
> Cheers,
> Till
>
> On Wed, Jun 14, 2017 at 2:40 PM, Jark Wu
I think that the integration of SQL and CEP would make a good FLIP.
Cheers,
Till
On Wed, Jun 14, 2017 at 2:40 PM, Jark Wu wrote:
> Hi,
>
> Do you think whether we should create a FLIP for this proposal to track
> progress?
>
> Regards,
> Jark
>
> 2017-06-13 16:59 GMT+08:00
Hi Fabian,
Thanks a lot. Agree that we can start working by adding the missing
features of the CEP library.
Best regards,
Dian
On Tue, Jun 13, 2017 at 4:26 PM, Fabian Hueske wrote:
> Hi,
>
> @Dian Fu: I gave you contributor permissions. :-)
>
> I don't think we have to wait
Hi,
@Dian Fu: I gave you contributor permissions. :-)
I don't think we have to wait for Calcite 1.13 to start working on the
missing features of the CEP library and extending the prototype.
We might want to wait with the integration into flink-table until Calcite
1.13 is out and we updated the
Hi Jark, Dian,
Thanks for bring up this discuss and share the prototype.
+1 to push this great feature forward!
Cheers,
SunJincheng
2017-06-13 15:34 GMT+08:00 Jark Wu :
> Thank you Yueting for pointing out the mistake in the prototype. I
> accidentally introduced it when
Thank you Yueting for pointing out the mistake in the prototype. I
accidentally introduced it when merge code.
I'm so glad to see so many people are interested in the feature. Let's work
out together to push it forward!
Cheers,
Jark Wu
2017-06-13 15:27 GMT+08:00 Liangfei Su
Hi Yueting & Dawid Wysakowicz,
Very glad that you're interested in this feature and you're definitely
welcome to join this work and also anyone else.:)
Best regards,
Dian
On Tue, Jun 13, 2017 at 2:35 PM, Dawid Wysakowicz <
wysakowicz.da...@gmail.com> wrote:
> Hi all,
>
> Integrating SQL with
Hi all,
Integrating SQL with CEP seems like a really nice idea. Unfortunately I had
time just for a brief look at the design doc, but it looks really cool and
thorough. Also will have a second run tomorrow and will try to provide more
comments. Anyway will be glad to help pushing the initiative
Hi Dian & Jark,
I checked out your prototype code, but it didn't pass the CEPITCase test in
the flink-table component.
It turns out that in the `MatchCodeGenerator.scala` file, line 74 should
use `${classOf[IterativeCondition.Context[_]].getCanonicalName}` instead of
Hi Fabian,
We have evaluated the missing features of Flink CEP roughly, it should not
be quite difficult to support them. Kostas, Dawid, what's your thought?
For supporting MATCH_RECOGNIZE, do you think we could create the JIRAs and
start to work right now or we should wait until the release of
Hi Jark,
Thanks for updating the design doc and sharing your prototype!
I didn't look at the code in detail, but the fact that it is less than 1k
LOC is very promising. It seems that most of the complex CEP logic can be
reused :-)
Adding a dependency on flink-cep should be fine, IMO. It is a very
Hi guys,
Good news! We have made a prototype for integrating CEP and SQL. See this
link
https://github.com/apache/flink/compare/master...wuchong:cep-on-sql?expand=1
You can check CepITCase to try the simple CQL example.
Meanwhile, we updated our design doc with additional implementation
Thanks for sharing your ideas with the community. I really like the design
document and think that it's a good approach to follow Oracle's SQL
extension for pattern matching. Looking forward to having support for SQL
with CEP capabilities :-)
Cheers,
Till
On Thu, Jun 8, 2017 at 8:57 AM, Jark Wu
Hi @Kostas, @Fabian, thank you for your support.
@Fabian, I totally agree with you that we should focus on SQL first. Let's
keep Table API in mind and discuss that later.
Regarding to the orderBy() clause, I'm not sure about that. I think it
makes sense to make it required in streaming
Thanks Dian and Jark for this proposal!
As you wrote, Till and I (and Kostas) have been thinking about this for
some time but haven't had time to work on this feature.
I think it would be a great addition and value add for Flink's SQL support
and Table API.
I read the proposal and think it is
Thanks a lot for opening the discussion!
This is a really interesting idea that has been in our heads
since the first implementation of the CEP library.
A big +1 for moving forward with this.
And as for the design document, I will definitely have a look
and comment there.
Kostas
> On Jun 7,
Sorry, I forgot to cc you guys @Fabian, @Timo, @Till, @Kostas
2017-06-07 15:42 GMT+08:00 Jark Wu :
> Hi devs,
>
> Dian and me and our teammates have investigated this for a long time. We
> think consolidating Flink SQL and CEP is an exciting thing for Flink. It'll
> make SQL
Hi devs,
Dian and me and our teammates have investigated this for a long time. We
think consolidating Flink SQL and CEP is an exciting thing for Flink. It'll
make SQL more powerful and give users the ability to easily and quickly
build CEP applications. And I find Flink community has also talked
Hi everyone,
Flink's CEP library is a great library for complex event processing, more
and more customers are expressing their interests in it. But it also has
some limitations that users usually have to write a lot of code even for a
very simple pattern match use case as it currently only
22 matches
Mail list logo