Supports Expression Language: true (will be evaluated using variable registry only)Message Type | message-type | | | Fully qualified name of the Protocol Buffers message type including its package (eg. mypackage.MyMessage). Please note it is the message type name from the .proto file, not the name of the generated Java class. The .proto files configured in 'Proto Directory' must contain the definition of this message type. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Output Field | output-field | | | Field of the message to output as the FlowFile content (e.g. customer.name). If not specified, the whole message will be converted to JSON and will be set in the FlowFile content. If empty string specified, no FlowFile content will be set. The latter can be used when message fields are extracted to FlowFile attributes instead of content (see dynamic properties). Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Dynamic Properties:
Supports Sensitive Dynamic Properties: No
Dynamic Properties allow the user to specify both the name and value of a property.
Name | Value | Description |
---|
message$<FIELD.PATH> | FlowFile attribute name | The property name specifies the field in the request message whose value will be added as a FlowFile attribute with the name specified in the property's value (e.g. message$customer.name => customerName). Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Relationships:
Name | Description |
---|
success | Protocol Buffers message converted successfully. |
failure | Protocol Buffers message failed to be converted. |
Reads Attributes:
None specified.Writes Attributes:
None specified.State management:
This component does not store state.Restricted:
This component is not restricted.Input requirement:
This component requires an incoming relationship.System Resource Considerations:
None specified.