I suspect the response body is JSON? When you want to get the token from it you can just use a JSONExtractor.
I suspect the response body is JSON? When you want to get the token from it you can just use a JSONExtractor.
Thanks Niels.
I can choose csv or json. I did discover through this thread that for CSV you need to write the content to disk first. I'll go that route if needed but it's noise in the workspace I'd rather avoid (6 transformers to achieve a single function).
When I try JSONExtractor I do bypass the name vs content issue I noted in opening, but the result is a single output of the entire json content instead of features.
Thanks Niels.
I can choose csv or json. I did discover through this thread that for CSV you need to write the content to disk first. I'll go that route if needed but it's noise in the workspace I'd rather avoid (6 transformers to achieve a single function).
When I try JSONExtractor I do bypass the name vs content issue I noted in opening, but the result is a single output of the entire json content instead of features.
Hard to be sure what you want or need without sample data, but it sounds you want to learn how to parse JSON. If you have multiple features in the response you can “explode” these into features using a JSONFragmenter.
Thanks Niels.
I can choose csv or json. I did discover through this thread that for CSV you need to write the content to disk first. I'll go that route if needed but it's noise in the workspace I'd rather avoid (6 transformers to achieve a single function).
When I try JSONExtractor I do bypass the name vs content issue I noted in opening, but the result is a single output of the entire json content instead of features.
Oh that's fun! Adding JSONFragmenter after JSONExtrator exploded a 4.2MB json into >100GB of temp .ffs features before running out of diskspace and crashing. I'll try to manually look over the json and see if there's anything to prevent me from sharing a sample.
The FFS file e...]\\AppData\\Local\\Temp\\wb-cache-fetch-assets-MxyZKs\\Main_JSONFragmenter -1 16 fo 0 FRAGMENTS 0 b6a49780b1913f42ae6f62418f64a71e24ce396e_68.ffs failed the CRC check. It is corrupt, and cannot be read
Thanks Niels.
I can choose csv or json. I did discover through this thread that for CSV you need to write the content to disk first. I'll go that route if needed but it's noise in the workspace I'd rather avoid (6 transformers to achieve a single function).
When I try JSONExtractor I do bypass the name vs content issue I noted in opening, but the result is a single output of the entire json content instead of features.
ok, here's the 1st 4 lines of the _response_body after HTTPCaller and before JSONExtractor: https://gist.github.com/maphew/efb83fa3f0bf835ae8b3fcf8253c84d6
