EN-US
Ask or search…
K
Links
Comment on page

Stream DB V1 (Deprecated)

Know the component and how to use it.
Stream DB V1 makes operations through the connection with a database, streaming data to a subpipeline that processes them.

Parameters

Take a look at the configuration options for the component:
Parameter
Description
Default value
Data type
Account
Account to be used by the component.
N/A
String
Database URL
Connection string to the database.
N/A
String
SQL Statement
SQL statement to be executed.
N/A
String
Column Name
Name of the columns to be read.
N/A
String
Coalesce
When activated, this option controls if the data objects are coalesced into a string or if an error is generated.
False
Boolean
Parallel Execution Of Each Iteration
Occurs in parallel with the loop execution.
False
Boolean
Fail On Error
When activated, this parameter suspends the pipeline execution only if there’s a severe occurrence in the iteration structure.
False
Boolean
Custom Connection Properties
Specific connection properties defined by the user.
N/A
N/A
Keep Connections
If activated, the option will keep the connections to the database for 30 minutes maximum; otherwise, it will be kept for 5 minutes only.
N/A
Boolean
Advanced
Advanced configurations.
N/A
N/A
Connection Test Query
SQL statement to be used before each connection is established - this is an optional parameter and must be applied to databases that don't have reliable information about the connection status.
N/A
String

Messages flow

Input

The component waits for a message in the following format:
{
"parameters": {
"name": "value"
...
}
}

Message "onProcess" structure

{
"column1":"data1",
"column2":"data2",
...
}

Output with error

{
"code": error_code,"error": error_message,
"processedId": the_id_column_value
}

Output

{
"total": 0,
"success": 0,
"failed": 0
}
  • total: total number of processed lines
  • success: total number of successfully processed lines
  • failed: total number of lines whose process failed
Important: when the lines are correctly processed, their respective subpipelines return { "success": true } for each of them.
Last modified 9d ago