jsgeronimo
New Contributor II
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Semantic URL Example
nganapathiraju: somepath What I did was POST to my Triggered Task URL https://elastic.snaplogic.com:443/api/1/rest/slsched/feed/org/myproject/path/exampleData/3 I wanted to catch the key value pair of exampleData: 3 so I placed it on the pipeline parameter as exampleData and then I used the mapper to catch and map it to my exampleData field (for my json). the output of the PATH_INFO is correct which is “exampleData/3”. or “examplePath”: “exampleData/3” but if what I wanted to get was the “exampleData”: “3”. is this possible with semantic URL? Thank you for responding.3.3KViews0likes5CommentsSemantic URL Example
Hi, I would like to know how to correctly pass data via Semantic URL (as a Triggered Task via URL)? Here is what I did: Edit Pipeline Properties: I created an exampleId variable, if I wanted to pass a value of 1 to the exampleId variable: https://elastic.snaplogic.com:443/api/1/rest/path/to/my/project/pipelineName/exampleId/1 What I have working is: https://elastic.snaplogic.com:443/api/1/rest/path/to/my/project/pipelineName/?exampleId=19.2KViews1like18CommentsRe: Using Azure Storage/Azure Blob Storage
Hi dmiller, we are using version snapsmrc414 - which i think is version 4.10 release according to this link: https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438714/Snap+Pack+Versions+by+Release Thanks! Still trying to figure out as to how it is working in Cyberduck and not in the snaplogic canvas.3.7KViews0likes3CommentsUsing Azure Storage/Azure Blob Storage
I am trying to create an Azure Blob Reader but I keep encountering this error: Error: Directory not found or access denied: wasb:///storage@janoswsl.blob.core.windows.net/; Reason: com.snaplogic.snaps.hadoop.BinaryAzureAccount cannot be cast to com.snaplogic.snaps.hadoop.KerberosAccount; Resolution: Please check if the directory exists, you have access right and all Snap properties and credentials are valid. Failure: Unable to read from wasb:///janoswsl.blob.core.windows.net/storage/globalweather.xml, Reason: java.io.IOException: Failed to open input stream for WASB path: wasb:///janoswsl.blob.core.windows.net/storage/globalweather.xml, detail: The specifed resource name contains invalid characters., Resolution: Please address the reported issue. I also tried replacing wasb with wasbs but I still get the same error. Here are some screenshots of my pipeline and I used cyberduck tool to verify I can successfully connect to the Azure storage. I am not sure if using a trial account for Azure is causing this. and a cyberduck screenshot6.2KViews0likes5Comments