@Igor: State from the CEP library (like what was the last observed event
for a certain ID or so) is kept in Flink's state mechanisms (the key/value
state)

Have a look at these docs for details:
  - Working with State:
https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/streaming/state.html
  - Fault tolerance in general:
https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/streaming/fault_tolerance.html
  - Changing how state is stored internally (via state backends):
https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/streaming/state_backends.html


On Tue, Mar 8, 2016 at 8:32 PM, Igor Berman <igor.ber...@gmail.com> wrote:

> Congratulations!
> Very nice work, very interesting features.
>
> One question regarding CEP: do you think it's feasible to define pattern
> over window of 1 month or even more?
> Is there some deep explanation regarding how this partial states are saved?
> I mean events that create "funnel" might be separated by very large
> periods of inactivity/noise
>
>
>
> On 8 March 2016 at 17:17, Kostas Tzoumas <ktzou...@apache.org> wrote:
>
>> Hi everyone!
>>
>> As you might have noticed, Apache Flink 1.0.0 has been released and
>> announced!
>>
>> You can read more about the release at the ASF blog and the Flink blog
>> -
>> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces88
>> - http://flink.apache.org/news/2016/03/08/release-1.0.0.html
>>
>> Don't forget to retweet and spread the news :-)
>> - https://twitter.com/TheASF/status/707174116969857024
>> - https://twitter.com/ApacheFlink/status/707175973482012672
>>
>> Check out the changelog and the migration guide, download the release,
>> and check out the documentation
>> - http://flink.apache.org/blog/release_1.0.0-changelog_known_issues.html
>> -
>> https://cwiki.apache.org/confluence/display/FLINK/Migration+Guide%3A+0.10.x+to+1.0.x
>> - https://cwiki.apache.org/confluence/display/FLINK/Stability+Annotations
>>
>> - http://flink.apache.org/downloads.html
>> - https://ci.apache.org/projects/flink/flink-docs-release-1.0/
>>
>> Many congratulations to the Flink community for making this happen!
>>
>> Best,
>> Kostas
>>
>
>

Reply via email to