|Term or Acronym
|A stream processing high volumes of data in batch(es) within a specific time span. It processes large amount of records in one transaction. For example, data file read via S3 bucket.
For batch streams, the 7799838 happens only when a stream is run.
A unidirectional 7799838 that processes finite units of input, for example, complete files or a fixed amount of rows in a database.
A function that collects data from a 7799838.
The process of Dazzler Cloud Edition acquiring data from a 7799838.
A communication mode where collectors initiate outgoing requests.
Custom references refer to an optional feature that is used with SAP-related functions. When enabled it allows users to specify one or more typeCode and id values in the relevant usage records.
|The process of parsing input from a 7799838 and converting it into records in a format that can be sent across a 7799838.
An endpoint to which data is sent from a 7799838.
The flush operation forces to pass the stored/buffered (aggregated) data to the next function in the stream.
|A Function that sends data to a given 7799838.
The process of sending data to a 7799838.
A Function accepts input, applies logic to it, and then returns a result. Functions may be stateful.
|HTTP Response Headers
This is an option found within the HTTP Client collector and processor function, intended to support the sending out of response headers in the network stream. The users can enter a custom value in the result header key and associated result key to configure the target web service.
A notification group is an email list to which automated messages regarding erroneous events related to streams are being sent. The content of the error messages include stream execution errors, missing files, and related events.
|Refers to the current record.
RegEx (Regular Expression)
The use of regular expressions implies the creation of custom schemes to which various operations can be executed.
|Stream processing data in real-time. The data size is unknown, infinite and continuous. During real-time streams, the data output rate is as fast as data input rate. When the incoming data is continuous and requires immediate response then in that case real-time streams are used. For example, data continuously send via HTTP collector.
For real-time streams, the 7799838 happens after every 60 seconds.
A representation of aggregated records that is stored before being flushed out.
A solution is a set of streams that together solve a particular customer problem.
|An 7799838 from which data is collected into a 7799838 using a given protocol and data format.
|Time To Leave (TTL)
This is a mechanism that limits the lifespan of data in an environment. It is used in functions like aggregation to express the date and time where a record expires.
|A method that allows to set a timer to the execution of a certain function. Timeouts allow for more efficient usage of limited resources. The basic idea is that in situations where a system must wait for something to happen, rather than waiting indefinitely, the waiting will be aborted after the timeout period has elapsed.
A transaction is a unit of data that is being processed inside a stream. The definition of a completed transaction is when the stream processes it without any errors. The transactions by design are limited to their specified data sources.
A transaction can refer to a file that is being processed in a stream or a result set from a query.
The data correction feature also creates transactions of reference and they are regarded as separate processes.
For more information refer to Transaction Safety.
|Transactions Per Second (TPS)
This is a metric showing the number of transactions per second (tps) that can be processed by a given web service. This value can be calculated using this formula:
Tps value for a function = (Total number of output events handled by the function) / (duration of the stream)