...
Limitations
None.
Known Issues
The When returning nonstandard types, the SQL statement will return a PGObject when returning nonstandard types. You must use the Execute Snap in these cases.
Behavior Change
Multiexcerpt fast include block macro | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| This Snap has at most one document input view. If the input view is defined, then the where clause can substitute incoming values for a given expression (in for example, to use it as a lookup). |
Output | Document |
|
| This Snap produces one document for each row in the table. After a query is executed, the query's results are merged into the incoming document, overwriting any existing keys' values. The original document is output if there are no results from the query. A second view can be added to push the metadata for the table as a document. The metadata document can then be passed into the second input view of AlloyDB Insert Snap so that the table is created in AlloyDB with a similar schema as the source table. |
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 while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. |
...