omair
Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Referencing snap, pipe variables from within an expression library
I’m trying to create an expression library function that needs access to both the snap and pipe variables. Can these variables be accessed directly from within the expression library function or must they be passed in as parameters? Right now my function looks like this: getHeader: (name) => match(pipe.flags.immediate_mode) { true => snap.original.load().get(name), _ => pipe.get("args",{}).get(name) } When I run this pipeline, I get the following error: {"error":"snap is undefined. Perhaps you meant: isNaN, jsonPath, JSON, String, _personsURL, parseInt","reason":null,"resolution":"Check the spelling of the variable"}SnapLogic Errors: Return custom payload and fail pipeline
Is it possible within SnapLogic to configure a pipeline to fail via a Snap but also to return a custom output back to the user (configured via a Mapper snap, e.g.) I have reviewed the video here: Framework: Error Handling & Retry Patterns and it appears that a SnapLogic pipeline can either: fail with limited control on the error message (e.g. using the Exit snap which allows for a text message) OR specify a detailed error message (e.g. via an error pipeline or directly)… in this case the pipeline is marked completed.6.6KViews1like6CommentsDesigner: Pretty JSON when exporting pipelines to assist with external version control systems
Use-case: I would like to use version control to store my pipeline assets. Organizational restrictions prevent the use of Github for version control. Right now the dev process is to export pipelines from designer and commit them to version control (Mercurial). The Designer pipeline export operation, minifies the pipeline JSON to a single line. This makes it impossible to do any diff comparisons or review pipeline changes within a diffing tool. Feature request: Pretty print JSON when exporting a pipeline from Designer:2KViews1like1CommentRe: Rest GET - Next URL with page=# syntax with no metadata
@dmiller : cjhoward18’s response above, i.e. For Next URL I believe you can use the expression: 'https:domain.com/object/page/' + (snap.out.totalCount + 1).toString() to have second request add 2, then 3, 4, 5, and so on. should be added to the pagination portion of the REST Get documentation. I’m working with an API that also does not include the current page number, nor next offset in the response, so implementing pagination requires incrementing the offset. I had to spend 15 minutes searching community before I came across this tip.2.8KViews0likes1CommentSnaplex stability / performance issues
I have a single feedmaster + single groundplex setup: Currently there are 70 active (ultra) pipelines and the groundplex is consuming ~1400 threads. There are additional ultra pipelines that the system is trying to initialize. However, we are encountering severe stability issues: we are seeing numerous pipelines failing to prepare in the dashboard new ultra pipelines take 15+minutes to initialize. Are there any configuration changes that can be made to improve system stability and increase responsiveness… Thanks.2.3KViews0likes1CommentStopping pipeline execution when REST snap fails in pipeline
I have a pipeline that retrieve data from an external REST API, performs some data transformations and returns the resulting data. Part of the data transformations require looks that rely on the inbound payload so I have a copy snap to enable the lookups. However, the problem is that when the REST snap itself fails (as shown in the image) the happy path flow (the Join snap and the Map Entity with Titles snap followng it) continues to execute. The error path is forwarded to an error pipeline as shown below: What is the simplest way of dropping the existing the happy path flow when the REST snap returns an error in the case above? Thanks,2.6KViews0likes2CommentsUpdating Feedmasters queue size max
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/809009264/Deploying+a+FeedMaster+Node has the following snippet: You can configure this value in the FeedMaster node’s properties file by specifying the limit in bytes: jcc.broker.disk_limit= 20971520 However the documentation is a little unclear on where this property should be set… are we supposed to: update the node properties through the UI (Manager)? update the c:\opt\snaplogic\etc\global.properties file and add it there? Thanks2.5KViews0likes1CommentCorrect way of restarting ultra pipelines
Hi, I’m writing to ask about the correct way to restart ultra pipelines. In our production environment we have 7 ultra tasks with 5 instances each. We went to the SnapLogic manager view and Disabled and Re-enabled all the tasks. In this case we saw that ~20 out of the 35 task instances were restarted with the others failing to restart. This leads me to believe that this is not a guaranteed way of restarting all pipeline task instances. Can someone tell me what is the correct way of restarting all the pipelines?3.5KViews0likes1Comment