Apama 10.3 | Apama Documentation | Developing Apama Applications | Developing Apama Applications in EPL | Defining Queries | Partitioning queries
Partitioning queries
Defining query keys
Defining actions as query keys
Query partition example with one input
Query partition example with multiple inputs
About keys that have more than one field
Based on the values of selected fields in incoming events, the correlator segregates events into many separate partitions. Partitions typically relate to real-world entities that you are monitoring such as bank accounts, cell phones, or subscriptions. For example, you can specify a query that partitions Withdrawal events based on their account number. Each partition could contain the Withdrawal events for one account. Typically, a query application operates on a huge number of partitions with a relatively small number of events in each partition.
Each partition is identified by a unique key value. You specify a key definition in each input definition in the query's inputs block. The key definition specifies one or more fields or actions in the event type you want to monitor. The number, order and type of the key fields must be the same in each input definition in a query.
A query operates on the events in the windows in each partition independently of the other partitions.
Note: Several restrictions are enforced on queries if a license file cannot be found while the correlator is running. See Running Apama without a license file.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.