What are the purposes of $property_map.input and $property_map.output in a *.slp file
I have downloaded a pipeline as a *.slp file and opened it in a text editor. Noticed that both $property_map.input and $property_map.output refer certain snaps in the pipeline. What’s purpose of following two objects: $property_map.input $property_map.output Why are those snaps singled out, for example “Mapper_FailedCertificatesList - output0”? Following is the snippet: "property_map": { "info": null, "input": { "7536ff22-1c0d-44c6-ada7-718de5a98634_input0": { "label": { "value": "Conditional_Certificates_Offers_Length - input0" }, "view_type": { "value": "document" } } }, "settings": { "param_table": { "value": }, "imports": { "value": [] } }, "output": { "ac14846d-7856-4e1d-9ca0-b519741a25b6_output0": { "view_type": { "value": "document" }, "label": { "value": "Error 400 Union - output0" } }, "2bfe809b-a4b7-4f9b-9007-5262ea6b0b58_output0": { "label": { "value": "Mapper_FailedCertificatesList - output0" }, "view_type": { "value": "document" } }, "36e341cd-bb8d-42d9-94f9-24eb72a812c8_output0": { "view_type": { "value": "document" }, "label": { "value": "Mapper_FailedCertificatesList - output0" } } }, I do noticed that snap “Mapper_FailedCertificatesList - output0” has io_stats object has value while most other snap don’t in the pipeline monitor API output. Here’s an example of the io_stats value: [ { "send_duration": 49923, "remote": "pa23sl-fmsv-ux02007.fsac5.snaplogic.net/172.29.66.28:8089", "bytes_recv": 0, "start_time": 1499885665780, "error_duration": 0, "bytes_sent": 1370, "recv_duration": 0, "error_count": 0, "type": "socket" }, { "send_duration": 149004, "remote": "pa23sl-fmsv-ux02000.fsac5.snaplogic.net/172.29.65.214:8089", "bytes_recv": 0, "start_time": 1499885663392, "error_duration": 0, "bytes_sent": 1178, "recv_duration": 0, "error_count": 0, "type": "socket" } ] This behavior can be seen in SnapRuntimeFlashlight-AllSnaps-RedeemV2.2.xlsx (80.0 KB). It is an aggregated view of the pipeline monitor api output of many ruuids for the same pipeline. Also attached the .slp file Redeem_Pl_V2.2_2017_07_12.slp.txt (212.8 KB) P.S. after post this, saw this in dashboard: and now reading https://doc.snaplogic.com/wiki/display/SD/Check+Pipeline+Execution+Statistics
Outside Community
Continuing the discussion from Stackoverflow – Snaplogic tag created: @dmiller @cstewart I have a strong feeling that no posts should be entertained outside of our community. We should keep our platform tightly knit so that any information is not available easily outside publicly. If posts and solutions are allowed outside, it would become polluted. There would be opponents to this idea who believe in widespread message in the internet world from marketing point of view but there is marketing to handle that. One example I would give is Oracle and Workday. Oracle - you can find anything out there on Google. Workday - Good luck if you find any relevant posting to its technology or even mere discussion of its platform publicly. They only expose information through their community. Whereas our documentation is public, Workday documentation is not. Its only available to its customers/partners. Just my two cents on it.How can a Join snap ever work in an ultra pipeline without using pipeExec?
In SL documenation about the Join snap, it has Support and limitations: Ultra pipelines: May work in Ultra Pipelines. Tried in vain to create an ultra pipeline contains a Join snap that works functionally. Hope someone can provide an example. Here are what have been tried: used left outer join. It doesn’t produce any output. childJoin_2017_05_17.slp (5.9 KB) used merge. It failed with error Document created by ‘Merge[07773f4c-3a75-46f5-a46c-65d205aa6cc0 – b6c35bc0-b3df-4cb7-b086-35007573a112]’ does not contain lineage information and cannot be used as output from an Ultra pipeline Resolution Use a Join snap to merge static documents into an Ultra input document or request that the snap be made Ultra-compatible childMerge_2017_05_17.slp (5.7 KB) Understand the we could move the Join inside a pipeExe, but that’s not what I wanted in this case.Pipeline queuing and Pipeline Exeute
Hello team, We have documentation regarding queueing of pipelines here: https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1439392/Pipeline+Queueing It notes: The SnapLogic control plane and data plane were improved in the Winter 2016/4.4 release to more gracefully handle certain overload conditions on a Snaplex. This change introduces a new “Queued” state for pipeline executions and adds properties to the Snaplex configuration to set the resource thresholds used to detect an overload. When an execution is in the Queued state, the control plane will try to start the execution when resources become available on the Snaplex. A pipeline will not stay in the Queued state forever; it will timeout after a while. A scheduled pipeline will timeout before the next scheduled execution or 4 hours, whichever comes first. A ForEach execution expires after 5 minutes. Not all methods of execution will result in a pipeline being put into the Queued state. Only executions started by a Scheduled Task or a ForEach Snap. My customer would like to know regarding the last sentence, what about executions that are started by a Pipeline Eecute - will that method of execution result in a pipeline being put into a queued state? I believe so, but I wanted to verify. Thanks RobNot able to use toggle endpoint to enable an ultra task
I am trying to use following toggle endpoint to enable or disable ultra task: snap = REST POST url = "https://elastic.snaplogic.com/api/1/rest/slsched/job/toggle%2F"+$snode_id http entity = {"snode_id":$snode_id,"enabled":true} I am getting: { "error_entity": { "query_string": "", "path": "/api/1/rest/slsched/job/toggle/5935c7e1bc9ffa5b8bd6883e", "response_map": { "error_list": [ { "message": "Expecting body argument for endpoint toggle_job: enabled" } ] }, "http_status": "400 Bad Request", "http_status_code": 400 } } What could I be doing wrong?Community folder in ConnectFasterInc
Folks We can create the sample pipelines for any solutions we create for SnapLogic Community questions. In ConnectFasterInc, I have created a project space/folder called _Community/SnapLogic. This will help in other snaplogicians to look at the same solution in case they want to refer or want to enhance.Rest post cookies
Continuing the discussion from Request Body in Rest API Pipeline: @tstack @dmiller Can you guys take a look at this? This request needs a Cookie to be sent across and authenticated via our REST POST snap. I have tried the same request in SOAPUI and it works. I was trying to get it to work in POSTMAN but even with Interceptor that handles Cookies, I was unable to do it. Can you guys suggest what else could be done? Here is my pipeline. https://elastic.snaplogic.com/sl/designer.html?pipe_snode=598b5f21a92066355787c461&active_org=ConnectFasterIncPassword with "&" in Rest Account
I recently had an issue where the password contained “&” in it and the end point which is a Auth Token server failed to validate it. I was not sure if the Auth Server failed to receive it in proper format or if our snap was transmitting it improperly. The workaround was to change the password replacing the “&” with another character such as “_”. Please note this for any REST related problems.
