Skip to main content

@terascope/job-components / index / OpConfig

Interface: OpConfig

Defined in: packages/types/dist/src/teraslice.d.ts:193

OpConfig is the configuration that user specifies for a Operation. The only required property is _op since that is used to find the operation.

Extended by

Indexable

[prop: string]: any

Properties

PropertyTypeDescriptionDefined in
_dead_letter_action?stringThis action will specify what to do when failing to parse or transform a record. The following builtin actions are supported: - "throw": throw the original error - "log": log the error and the data - "none": (default) skip the error entirely If none of the actions are specified it will try and use a registered Dead Letter Queue API under that name. The API must be already be created by a operation before it can used.packages/types/dist/src/teraslice.d.ts:217
_encoding?DataEncodingUsed for specifying the data encoding type when using DataEntity.fromBuffer. Default json.packages/types/dist/src/teraslice.d.ts:205
_opstringThe name of the operationpackages/types/dist/src/teraslice.d.ts:195
api_name?stringThe name of the api used by this operationpackages/types/dist/src/teraslice.d.ts:197
connection?stringThe name of connection, should match the same as listed in your sysconfigs.connectorspackages/types/dist/src/teraslice.d.ts:199