Forum Discussion
@Supratim Also when I run the snap, I can’t get any intermediate results or only empty json is being returned every time?
I can see the files in the debug trace and they look fine but when I check snap results, they are empty.
Also, when using REST API(GET/POST) snaps, the intermediate results in the snaps are not there.
@anayak Are you referring “Run Snap” as run pipeline? If you create an API which accept data (POST) and you run pipeline will not work. Either you have to use json generator with expected payload at the very beginning of the pipeline and once development done remove/disconnect/disable it or use Record-Replay snap instead of Json generator, and send expected payload via postman then start your development.
If you want to test your API by Rest snap during development, make sure execution label of all snap you used in your main pipeline (implementation ) should be validate and execute.
Welcome @ausman - you are correct that you cannot “save” a value back to pipeline parameters, but there are a some easy ways to do what you are looking to do.
One simple method is to have a main pipeline that reads from the SQS queue then calls a child pipeline to do the work on that file. Then the main pipeline can use the $original object value that returns from the Pipeline Execute snap to get the object that was originally passed into the child pipeline.
Another way (which in my opinion is a little more cumbersome) is to use the Copy snap after the SQS read and a Join snap using the Merge merge type after you have completed the work on the file so you can re-use that original value that was returned from the SQS queue.
I’m sure some other clever folks could give you other ways to solve the same issue, but these are pretty simple to understand and implement.
Hope this helps!
Related Content
- 4 years ago
- 8 years ago