[jira] [Created] (FLINK-7172) Add a event logical id field to ValueTimeWrapper
Yueting Chen created FLINK-7172: --- Summary: Add a event logical id field to ValueTimeWrapper Key: FLINK-7172 URL: https://issues.apache.org/jira/browse/FLINK-7172 Project: Flink Issue Type: Improvement Reporter: Yueting Chen In order to address FLINK-7169, we need to know the logical order of the input events. This issue aims to add a logical id field to ValueTimeWrapper. This requires some modifications from `AbstractKeyedCEPPatternOperator` to `ValueTimeWrapper` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FLINK-7169) Support AFTER MATCH SKIP function in CEP library API
Yueting Chen created FLINK-7169:
---
Summary: Support AFTER MATCH SKIP function in CEP library API
Key: FLINK-7169
URL: https://issues.apache.org/jira/browse/FLINK-7169
Project: Flink
Issue Type: Task
Components: CEP
Reporter: Yueting Chen
Assignee: Yueting Chen
In order to support Oracle's MATCH_RECOGNIZE on top of the CEP library, we need
to support AFTER MATCH SKIP function in CEP API.
There're four options in AFTER MATCH SKIP, listed as follows:
1. AFTER MATCH SKIP TO NEXT ROW: resume pattern matching at the row after the
first row of the current match.
2. AFTER MATCH SKIP PAST LAST ROW: resume pattern matching at the next row
after the last row of the current match.
3. AFTER MATCH SKIP TO FIST *RPV*: resume pattern matching at the first row
that is mapped to the row pattern variable RPV.
4. AFTER MATCH SKIP TO LAST *RPV*: resume pattern matching at the last row that
is mapped to the row pattern variable RPV.
I think we can introduce a new function to `CEP` class, which takes a new
parameter as AfterMatchSKipStrategy.
The new API may looks like this
{code}
public static PatternStream pattern(DataStream input, Pattern<T, ?>
pattern, AfterMatchSkipStrategy afterMatchSkipStrategy)
{code}
We can also make `SKIP TO NEXT ROW` as the default option, because that's what
CEP library behaves currently.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: Request for contributor permissions
Hi Chesnay, I got the permissions. Thanks so much. Regards, Yueting Chen On Sun, Jul 9, 2017 at 10:31 PM, Chesnay Schepler <ches...@apache.org> wrote: > You now have contributor permissions. > > Oddly enough I still couldn't find you using the username, but the full > name did the trick. > > > On 09.07.2017 03:38, Yueting Chen wrote: > >> Hi Chesnay, >> >> I double checked my username, here's my jira profile details: >> >> username: ychen >> fullname: Yueting Chen >> >> Would you please check again ? >> >> Thanks, >> Yueting Chen >> >> >> On Sat, Jul 8, 2017 at 1:54 PM, Chesnay Schepler <ches...@apache.org> >> wrote: >> >> Hello, >>> >>> i tried but there is no user named "ychen". Please double check the name. >>> >>> Regards, >>> Chesnay Schepler >>> >>> >>> On 07.07.2017 15:54, Yueting Chen wrote: >>> >>> Hi devs, >>>> >>>> I am very interested in Flink and willing to contribute to it. Could >>>> anybody give me contributor permissions? My jira username is "ychen". >>>> Thanks! >>>> >>>> Regards, >>>> Yueting Chen >>>> >>>> >>>> >
Re: Request for contributor permissions
Hi Chesnay, I double checked my username, here's my jira profile details: username: ychen fullname: Yueting Chen Would you please check again ? Thanks, Yueting Chen On Sat, Jul 8, 2017 at 1:54 PM, Chesnay Schepler <ches...@apache.org> wrote: > Hello, > > i tried but there is no user named "ychen". Please double check the name. > > Regards, > Chesnay Schepler > > > On 07.07.2017 15:54, Yueting Chen wrote: > >> Hi devs, >> >> I am very interested in Flink and willing to contribute to it. Could >> anybody give me contributor permissions? My jira username is "ychen". >> Thanks! >> >> Regards, >> Yueting Chen >> >> >
Request for contributor permissions
Hi devs, I am very interested in Flink and willing to contribute to it. Could anybody give me contributor permissions? My jira username is "ychen". Thanks! Regards, Yueting Chen
Re: [DISCUSS]: Integrating Flink Table API & SQL with CEP
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
`${classOf[IterativeCondition.Context[_]]}`.
I've also read your desgin document and it looks fine to me. Actually, I am
working on the same thing recently, I think maybe we can work together to
push this forward.
Thanks,
Yueting Chen
On Tue, Jun 13, 2017 at 10:44 AM, Dian Fu <dia...@apache.org> wrote:
> 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 calcite
> 1.13?
>
> Btw, could you help to add me(dian.fu) to the contributor list, then I can
> assign the JIRAs to myself? Thanks a lot.
>
> Best regards,
> Dian
>
> On Tue, Jun 13, 2017 at 3:59 AM, Fabian Hueske <fhue...@gmail.com> wrote:
>
> > 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 slim
> > library with almost none external dependencies.
> >
> > Regarding the missing features of Flink CEP that you listed in the design
> > doc, it would be good to get some in put from Kostas and Dawid which are
> > the main contributors to CEP.
> > Do you have already plans regarding some of the missing features or can
> you
> > assess how hard it would be to integrate them?
> >
> > Cheers, Fabian
> >
> > Btw. The Calcite community started a discussion about releasing Calcite
> > 1.13. So, the missing features might soon be available.
> >
> > 2017-06-12 14:25 GMT+02:00 Jark Wu <j...@apache.org>:
> >
> > > 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
> > detail,
> > > including how
> > > to translate MATCH_RECOGNIZE into CEP API, and the features needed to
> add
> > > to Flink CEP,
> > > and the implementation plan. See the document
> > > https://docs.google.com/document/d/1HaaO5eYI1VZjyhtVPZOi3jVzikU7i
> > > K15H0YbniTnN30/edit#heading=h.4oas4koy8qu3
> > >
> > > In the prototype, we make flink-table dependency on flink-cep. Do you
> > think
> > > that is fine?
> > >
> > > What do you think about the prototype and the design doc ?
> > >
> > > Any feedbacks are welcome!
> > >
> > > Cheers,
> > > Jark Wu
> > >
> > >
> > > 2017-06-08 17:54 GMT+08:00 Till Rohrmann <trohrm...@apache.org>:
> > >
> > > > 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 <j...@apache.org> wrote:
> > > >
> > > > > 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 mode(either order by
> > > rowtime
> > > > > or order by proctime). But CEP also works in batch mode, and not
> > > > necessary
> > > > > to order by some column. Nevertheless, we can support CEP on batch
> > SQL
> > > > > later.
> > > > >
> > > > >
