Input 

Document

• Min: 0

• Max: 1

• Mapper

• JSON Generator

The snap requires the user to input a gRPC server endpoint to connect to, and then select the specific service and method to access.

Output

Document

• Min: 0

• Max: 1

• Mapper

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Label*

Default Value: gRPC Client
Example: gRPC Client

String

Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Server endpoint

Default Value: N/A
Example:

String/Expression

Specify the server to which the requests are sent.

gRPC service

Default Value: N/A
Example: helloworld.HelloWorld

String/Expression/Suggestion

Specify the gRPC request to be made.

gRPC method

Default Value: N/A
Example: helloworld.HelloWorld.SayHelloClientStream

String/Expression/Suggestion

Specify the gRPC method request.

Snap Execution

Default Value: 
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

• Validate & Execute: Performs limited execution of the Snap based on Preview Document Count value in User settings and generates a data preview during pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during pipeline runtime.

• Execute only: Performs full execution of the Snap during pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.

Account validation failed.

The Pipeline ended before the batch could complete execution due to a connection error.

Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.