Page History
...
The annotations supported for execution plans are as follows.
Annotation | Description | Example |
---|---|---|
| The name of the execution plan. | @Plan:name('ExecutionPlan') |
@plan:description (<description about execution plan>) | This provides a description about the execution plan. Details such as the business requirement of the execution plan can be mentioned here. |
|
@plan:async (bufferSize=<event queue size>) | WSO2 DAS has a disruptor based implementation to handle streams that are disabled by default. This annotation can be used to enable the disruptor at execution plan level that affects all the streams in the execution plan. The buffer size is an optional parameter. The default buffer size is 1024 . | @plan:async(bufferSize=2) |
@async(bufferSize=<event queue size>) | Using this you can enable the disruptor only for a specific event stream. The event flow of the specified stream passes through the disruptor when enabled. |
|
@import (<DAS stream definition>) | This is used to import a DAS event stream definition and map it to a Siddhi stream definition. For more information about event stream definitions, see Understanding Event Streams and Event Tables. |
|
@export (<DAS stream definition>) | This is used to export a Siddhi event stream definition and map it to a DAS event stream definition. |
|
Step 1: Add execution plan info
...
Query expressions are event processing logic written in Siddhi Query Language. When defining more than one query, each query should end with a semi colon.
Step 4. Export streams
Anchor | ||||
---|---|---|---|---|
|
Defines the mappings between the exported (output) stream of the Siddhi runtime to one of the available event streams (defined inside query expressions). The parameters are as follows.
...