This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
For triggered tasks, the username field will show the user who created the task, the pipeline actually runs as the task owner. A change to show the task invoker username was done a few releases back. It is displayed as a new property called Remote Us...
The database lookup pattern would work well with an OLTP database, which has low query startup costs and is optimized for single record operations. With a data warehouse like Snowflake which is optimized for analytical queries, the query startup cost...
The Snowflake Lookup snap covers this functionality. That will allow lookup on any number of ids, it will internally batch as required. Also, Lookup snap will use bind parameters, avoiding possible issues with SQL Injection which can happen with a SQ...
Using the Group By N snap will work fine for smaller document sizes and document counts. Since grouping combines multiple documents and creates larger documents in memory, that approach is not recommended when document sizes or counts are large.
The ...
A load balancer needs to be provisioned for such scenarios where APIs are triggered on the Snaplex nodes externally. The Snaplex nodes should not be exposed to the external network, all requests to the Snaplex should come through the load balancer.
T...
