Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for temporal events (CEP) #49

Open
snikolayev opened this issue Mar 14, 2017 · 5 comments
Open

Add support for temporal events (CEP) #49

snikolayev opened this issue Mar 14, 2017 · 5 comments

Comments

@snikolayev
Copy link
Member

snikolayev commented Mar 14, 2017

Complex event processing centers around the notion of events arriving in streams. These events are correlated with each other based on the time of their occurrence; formally, these correlations are defined in terms of temporal relationships.
When it pertains to rules engines and the Rete network, it is important to recognize and retract events that can no longer satisfy any temporal relationship.
This feature aims at enabling such capabilities in NRules, namely:

  • Add the notion of an event (that has a time of occurrence and potentially duration)
  • Add the notion of a clock
  • Support temporal relationships between events (i.e. before, after, during, overlaps, within, etc.)
  • Support window functions over event streams
  • Support automatic garbage collection (retraction) of events that cannot satisfy any temporal relationships
@snikolayev snikolayev changed the title Placeholder Add support for temporal events (CEP) Mar 15, 2017
@promontis
Copy link

What is your view on this? What are you ideas for the future?

@snikolayev
Copy link
Member Author

@promontis see updated description. LMK if you have any ideas on this or want to discuss any feature on this list.

@AnisTss
Copy link

AnisTss commented Mar 12, 2019

Any updates on this ? We are planning to use NRules in a business project and this feature is crucial.

@snikolayev
Copy link
Member Author

This one is going to take a while, as this is a massive change. I wouldn't put that on the critical path of your project.

@AnisTss
Copy link

AnisTss commented Mar 13, 2019

@snikolayev Thank you for your responsiveness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants