nodes/generated

Interface KafkaTriggerNodeParameters

Source


interface KafkaTriggerNodeParameters {
    allowedStatuses?: (
        | "new"
        | "error"
        | "unknown"
        | "canceled"
        | "crashed"
        | "running"
        | "success"
        | "waiting"
    )[];
    groupId?: string;
    options?: {
        allowAutoTopicCreation?: boolean;
        autoCommitInterval?: number;
        autoCommitThreshold?: number;
        batchSize?: number;
        eachBatchAutoResolve?: boolean;
        errorRetryDelay?: number;
        fetchMaxBytes?: number;
        fetchMinBytes?: number;
        fromBeginning?: boolean;
        heartbeatInterval?: number;
        jsonParseMessage?: boolean;
        keepBinaryData?: boolean;
        maxInFlightRequests?: number;
        onlyMessage?: boolean;
        parallelProcessing?: boolean;
        partitionsConsumedConcurrently?: number;
        rebalanceTimeout?: number;
        returnHeaders?: boolean;
        sessionTimeout?: number;
    };
    resolveOffset?: | "onCompletion"
    | "onSuccess"
    | "onStatus"
    | "immediately";
    schemaRegistryUrl?: string;
    topic?: string;
    useSchemaRegistry?: boolean;
}

Properties§

§readonly allowedStatuses?: (
    | "new"
    | "error"
    | "unknown"
    | "canceled"
    | "crashed"
    | "running"
    | "success"
    | "waiting"
)[]

Default: ["success"]

§readonly groupId?: string

ID of the consumer group

§readonly options?: { ... }

Default: {}

§readonly resolveOffset?: "onCompletion" | "onSuccess" | "onStatus" | "immediately"

Select on which condition the offsets should be resolved. In the manual mode, when execution started by clicking on Execute Workflow or Execute Step button, offsets are always resolved immediately after message received. Default: "onCompletion"

§readonly schemaRegistryUrl?: string

URL of the schema registry. Only used when no Schema Registry credential is selected.

§readonly topic?: string

Name of the queue of topic to consume from

§readonly useSchemaRegistry?: boolean

Whether to use Confluent Schema Registry