기본 보기
Search
Option name
Type & Default Value
Description
boolean: false
Whether to use event time or processing time as the timestamp for an event. If event time is used, the timestamp will be extracted from the payload. The timestamp filed must be specified by the stream definition.
int64:0
When working with event-time windowing, it can happen that elements arrive late. LateTolerance can specifiy by how much time(unit is millisecond) elements can be late before they are dropped. By default, the value is 0 wich means late elements are dropped.
int: 1
A rule is processed by several phases of plans according to the sql statement. This option wil specify how many instances will be run for each plan. If the value is bigger than 1, the order of the messages may no be retained.
int: 1024
Specify how many messages can be buffered in memor for each plan. If the buffered messages exceed the limit, the plan will block message receiving until the buffered messages have been sent out so that the buffered size is less than the limit. A bigger value will accommodate more throughput but will also take up more memory footprint.
bool: false
Specify whether the meta data of an event will be sent to the sink. If true, the sink can get meta data information.
int: 0
Specify the qos of the stream. The options are 0: At most once; 1: At least once and 2: Exactly once. If qos is bigger than 0, the checkpoint mechanism will be activated to save states periodically so that the rule can be resumed from errors.
int: 300000
Specify the time interval in milliseconds to trigger a checkpoint. This is only effective when qos is bigger than 0.
COUNT7