Twitter Input: Controlling Fields to Ingest

The Twitter input will create well over 1k fields if left to its own devices. I have a mutate in my pipeline to remove a few hundred, unfortunately, it's kind of a resource hog to do it this way. Is there another, more effective way to control what fields are pulled/processed? I feel like this is gonna be a stupid easy thing to fix...

Have a look a the prune filter.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.