Forum Discussion
If you’re writing to a file, one option would be to put a Mapper and a second FileWriter after the first FileWriter. The second writer would then be configured to Append to the file instead of overwriting it. The Mapper would be configured with a binary output view and maps the string </import>
to $content
. However, not all filesystems support appending to the file.
I have to ask, though… Based on your screenshot, it looks like you’re writing XML? Can you use an XML Formatter? Or, is it XML encapsulated in CSV?
[quote=“tstack, post:2, topic:5774”]
a file, one option would be to put a Mapper and a second FileWriter after the first FileWriter. The second writer would then be configured to Append to the file instead of overwriting it. The Mapper would be configured with a binary output view and maps the string </import>
to $content
. However, not all filesystems support appending to the file.
I have to ask, though… Based on your s
ita XML formatted csv file.
This is awesome @koryknick, this sheds some light. I’m going to assume the JSON Formatter snap is also in that list as that was the one that did it for me. Although I do also have a gate snap but the plex didn’t started falling over until I added the JSON Formatter so it sounds like a combination of memory intensive snaps.
Now that I think about it, it might not even be just memory intensive snaps but enough snaps to cause the heap size to go over it’s limit.
Fortunately I found a better alternative but I’m interested if you developed a method into determining ways to throttle read snaps or is throwing ram at the plex your conclusion?
Thanks
Related Content
- 2 years ago
- 3 months ago
- 6 months ago