WSO2 Complex Event Processor is succeeded by WSO2 Stream Processor. To view the latest documentation for WSO2 SP, see WSO2 Stream Processor Documentation.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TermDefinition
Event StreamA logical series of events ordered in time.
Event Stream DefinitionThis defines event streams. An event stream has a unique name and a set of attributes assigned specific types, with uniquely identifiable names defining its schema.
EventAn event is associated with only one event stream, and all events of that stream have an identical set of attributes assigned specific types (or the same schema). An event contains a timestamp and the attribute values according to the schema.
AttributeAn attribute has a unique name within the event stream. The attribute type can be string, int, long, float, double, bool or object.
QueryA logical construct that derives new streams by combining existing streams. A query contains one or more input streams, handlers to modify those input streams, and an output stream to which it publishes its output events.
PartitionA logical container that processes a subset of the queries based on a pre-defined rule of separation.
Event TableA structured representation of stored data, allowing stored data to be accessed and manipulated at runtime.

...

Info

Connection instructions that can be used with "From" annotation:  

cluster.name : Hazelcast cluster/group name [Optional]  (i.e cluster.name='cluster_a').
      
cluster.password : Hazelcast cluster/group password [Optional]  (i.e cluster.password='pass@cluster_a').
      
cluster.addresses : Hazelcast cluster addresses (ip:port) as a comma separated string [Optional, client mode only] (i.e cluster.addresses='192.168.1.1:5700,192.168.1.2:5700').
      
well.known.addresses : Hazelcast WKAs (ip) as a comma separated string [Optional, server mode only] (i.e well.known.addresses='192.168.1.1,192.168.1.2').
      
collection.name : Hazelcast collection object name [Optional, can be used to share single table between multiple EPs] (i.e collection.name='stockTable').

...

For more information about In-memory event tables, see Sample 0106 - Using in-memory event tables.

For more information about RDBMS event tables, see Sample 0107 - Using RDBMS event tables.

Insert into

Query for inserting events into table is similar to the query of inserting events into event streams, where we will be using "insert into <table name>" code snippet. To insert only the specified output event category use "current events", "expired events" or "all events" keywords between 'insert' and 'into' keywords. 

...

Refer following for implementing different types of Siddhi extensions with examples