Docs Connect Components Processors redpanda_data_transform redpanda_data_transform Beta Available in: Self-Managed Executes a Redpanda Data Transform as a processor Introduced in version 4.31.0. Common Advanced # Common config fields, showing default values label: "" redpanda_data_transform: module_path: "" # No default (required) input_key: "" # No default (optional) output_key: "" # No default (optional) input_headers: include_prefixes: [] include_patterns: [] output_metadata: include_prefixes: [] include_patterns: [] # All config fields, showing default values label: "" redpanda_data_transform: module_path: "" # No default (required) input_key: "" # No default (optional) output_key: "" # No default (optional) input_headers: include_prefixes: [] include_patterns: [] output_metadata: include_prefixes: [] include_patterns: [] timestamp_ms: ${! timestamp_unix_milli() } # No default (optional) timeout: 10s max_memory_pages: 1600 This processor executes a Redpanda Data Transform WebAssembly module, calling OnRecordWritten for each message being processed. You can find out about how transforms work here: https://docs.redpanda.com/current/develop/data-transforms/how-transforms-work/ Fields module_path The path of the target WASM module to execute. Type: string input_key An optional key to populate for each message. This field supports interpolation functions. Type: string output_key An optional name of metadata for an output message key. Type: string input_headers Determine which (if any) metadata values should be added to messages as headers. Type: object input_headers.include_prefixes Provide a list of explicit metadata key prefixes to match against. Type: array Default: [] # Examples include_prefixes: - foo_ - bar_ include_prefixes: - kafka_ include_prefixes: - content- input_headers.include_patterns Provide a list of explicit metadata key regular expression (re2) patterns to match against. Type: array Default: [] # Examples include_patterns: - .* include_patterns: - _timestamp_unix$ output_metadata Determine which (if any) message headers should be added to the output as metadata. Type: object output_metadata.include_prefixes Provide a list of explicit metadata key prefixes to match against. Type: array Default: [] # Examples include_prefixes: - foo_ - bar_ include_prefixes: - kafka_ include_prefixes: - content- output_metadata.include_patterns Provide a list of explicit metadata key regular expression (re2) patterns to match against. Type: array Default: [] # Examples include_patterns: - .* include_patterns: - _timestamp_unix$ timestamp_ms Set a timestamp (in milliseconds) for each message (optional). When left empty, the current timestamp is used. This field supports interpolation functions. Type: string # Examples timestamp_ms: ${! timestamp_unix_milli() } timestamp_ms: ${! metadata("kafka_timestamp_ms") } timeout The maximum period of time for a message to be processed Type: string Default: "10s" max_memory_pages The maximum amount of wasm memory pages (64KiB) that an individual wasm module instance can use Type: int Default: 1600 Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution rate_limit redis