adding state query
@@ -256,6 +256,19 @@ Note: Despite of the optimizations, a join query is quite expensive when it come
![State Input Stream Query (Pattern & Sequence)](../images/architecture/siddhi-query-state.png "State Input Stream Query (Pattern & Sequence)")
+State input stream query runtime is generated for pattern and sequence queries. This consume events from one or more Stream Junctions
+via ProcessStreamReceivers. There will be a ProcessStreamReceiver and a set of basic processors for each condition defined in the query.
+When ProcessStreamReceiver consume events they update the existing states generated by previous conditions with the incoming events or
+if its for the first condition in the query then it creates a new state and update that with the incoming event. This is then passed
+to basic processors for to perform filter and transformation operations, the states
+that passes the basic processors are consumed by the PostStateProcessor and stored at the PreStateProcessor of the following pattern or
+sequence condition evaluations. When the state reaches the final condition's PostStateProcessor
+the output event is generated by QuerySelector and emitted as output.
+
+## Siddhi Partition Execution
+
+Partition is a wrapper around one or more siddhi queries
+
## Siddhi Event Formats
Siddhi has three event formats.
@@ -288,6 +301,7 @@ and letting new events to be inserted.
+
How query is compiled?
