nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jamie Wang <>
Subject RE: [EXTERNAL] - Re: GetTwitter to stream tweets instead pull
Date Thu, 04 May 2017 23:18:53 GMT
Hi Joey,

Thanks for the information. The name actually plays only a small part as you indicated. But
I sort of got convinced it is pulling after reading the help documentation for GetTwitter.
You can see it here:
The line "Pulls status changes from Twitter's streaming API" sort of got me to believe it
is a pull instead streaming. Also it'd be a good idea if possible to add a line to explicitly
document it is actually streaming. Thanks again for your note and my apology for the late


From: Joey Frazee []
Sent: Wednesday, May 03, 2017 12:51 PM
Subject: [EXTERNAL] - Re: GetTwitter to stream tweets instead pull

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<>

I’ll admit the name might be a little confusing since the Get might suggest it’s hitting
one of the REST<>
resources periodically instead of using a long-term HTTP connection.


On May 3, 2017, at 2:00 PM, Jamie Wang <<>>


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?


View raw message