Each shape in the Palette creates a specific type of stream or window, adapter, connection, reusable schema or module, or a store, to create a data flow.
Shape | Purpose | Usage |
---|---|---|
Connector |
Creates flows between streams and windows, establishes references between streams and shared components, or attaches notes to shapes. |
Click to select the connector tool, then click each of the shapes in the diagram to be connected.. |
Note | Creates a comment on the diagram only. This comment does not appear in the CCL file. | Documents additional user generated information in the SAP Sybase ESPAuthoring perspective for a project in Studio. |
The entry point for unkeyed event streams into a project. Receives data from either an input adapter or an external publisher. | A stream does not retain any data and does not have a state. Data in an input stream is not keyed. | |
|
Applies a continuous query to data arriving from another stream or window to produce a new stream. | Streams do not retain data and do not
have keys. They are "insert only," meaning that their output consists
only of inserts. Input must be a stream or a stream-window join. By default, new streams (including derived streams) are output, so they are visible to external subscribers. You can change the property to local. |
|
Applies a continuous query to data arriving from another stream or window. Retains data, and retention rules can be set. | Data must be keyed so that every row has a unique key. Processes inserts, updates, and deletes both as local and output. You can use the toolbar to change the output to local, if you do not want it visible to external subscribers. |
|
Applies a continuous query downstream from a window where there is no need to retain state but there is a need to preserve insert, update, and delete operations. | Can be used where a computation, filter, or union must be performed, but where a state does not need be maintained. Use the toolbar to change the derived delta stream to local if needed. |
The entry point for event streams into
a project where incoming events have primary keys and there is a desire
to maintain a window of event data. Supports opcodes (insert, update,
delete, upsert). Use this as an entry point for event streams if:
|
Window size can be set by row count with a fixed number of input records, or by time with records being kept for a specified period. The window must be keyed, that is, every row must have a unique key value. |
|
A programmable operator that uses custom SPLASH scripts to process incoming events. | A Flex operator can take input from any number of streams and/or windows and will produce a new derived stream or window (either local or output). | |
Takes input from a single stream or window and groups records using a common attribute. Produces a single output record for each group. Uses aggregate functions like sum(), count(), and so on. | Always creates a new window. Requires a GROUP BY element. You can optionally set window size using retention rules. | |
Takes input from a single source and computes a new record for every record received. Allows you to change the schema on events, computing new fields and changing existing fields. | Produces a derived stream when the input is a stream. Produces a derived delta stream when the input is a window. | |
Takes input from a single source and applies a filter. Creates a stream of records that match the filter criteria. | Produces a derived stream when the input is a stream. Produces a derived delta stream when the input is a window. | |
Takes input from two or more sources and joins them based on common data elements. | See related information in this guide and the Programmers Guide for join support details. | |
Takes input from two or more sources and detects patterns of events. One output record is produced every time a pattern is detected. | Detects patterns in the incoming data. See related information in the Programmers Guide. | |
Merges input from two or more sources. One ouput record is produced for every input record. | All inputs must have a common schema. | |
Represents a CCL CREATE SCHEMA statement. Reusable definition of column structure that can be referenced by streams and windows. | A schema defined outside of an object that can be used in multiple places, since any number of streams and windows can reference a single named schema. | |
Represents a CCL CREATE MODULE statement. Creates a new module that can be used in one or more places in the project. | A module can contain all the same elements as a project and provides for reuse. | |
Stores data held in windows. Provides disk-based recovery but is slower than a memory store | By default, new windows are assigned to a memory store. Where recoverability of data in a window is required, create a log store and assign the window to it. | |
Stores data held in windows. | Faster than a log store but does not
recover data after shutdown.
|
|
Connects an input stream or input window to an external data source. | Must be connected to either an input stream or input window. To use schema discovery—that is, to import the schema from the source—add the input adapter first, and then use schema discovery to create a connected input stream or window with the imported schema. | |
Connects an output stream or window to a destination. | Must be connected to either an output stream or an output window. | |
A CCL element that establishes a reference from an external database table to a project in ESP. Use references - in joins and in SPLASH programs - inside a module as well as within the main body of your project. | Can be used for data lookup and to enrich data streaming in ESP with information permanently stored in an external database table. For example, customer address and credit card information. For schema discovery, datatypes in the source schema for the reference must be compatible with those found in the external database table the reference queries. If incompatible, unexpected behavior such as an abnormal shutdown can occur. |