|Event Stream||A logical series of events ordered in time.|
|Event Stream Definition||This 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.|
|Event||An 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.|
|Attribute||An attribute has a unique name within the event stream. The attribute type can be string,|
|Query||A 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.|
|Partition||A logical container that processes a subset of the queries based on a pre-defined rule of separation.|
|Event Table||A structured representation of stored data, allowing stored data to be accessed and manipulated at runtime.|
Connection instructions that can be used with "From" annotation:
cluster.name : Hazelcast cluster/group name [Optional] (i.e cluster.name='cluster_a').
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