Jamie, can you explain a little bit more about what you’re looking for? The GetTwitter processor is accessing the spritzer/decahose/firehouse, what have you, via Twitter’s Hosebird library. This library is indeed streaming the Tweets from their sample and filter APIs in the usual way with a persistent, chunk-encoded HTTP connection to https://stream.twitter.com/1.1/statuses/sample.json and https://stream.twitter.com/1.1/statuses/filter.json.
I’ll admit the name might be a little confusing since the Get might suggest it’s hitting one of the REST https://api.twitter.com/1.1/statuses/ resources periodically instead of using a long-term HTTP connection. -joey > On May 3, 2017, at 2:00 PM, Jamie Wang <[email protected]> wrote: > > Hi, > > I understand the built-in processor GetTwitter is a pull. Are there streaming > based processor for getting Tweets available? If no, any suggestions on how > would l go by to build one? > > Thanks > Jamie
