generally working now. except that every time it runs, it returns one and exactly one result .json file. i find it hard to believe that there is exactly one tweet meeting my criteria ever 30 seconds. ... View more

I've just finished reading up on twitter's API and perhaps rate-limiting is the issue. I'm using a template pulled from HWX and it looks like it had the scheduling set to zero seconds. I have increased it to 30 seconds and still it does not work. Will reset my keys and see if that fixes it. perhaps twitter cuts off access for those identifiers. What is a "reasonable" schedule time that won't run into the rate limit? Here are some log messages: 2016-07-27 05:38:49,352 INFO [hosebird-client-io-thread-0] com.twitter.hbc.httpclient.ClientBase GetTwitter[id=b2e83358-2e38-42c5-88a7-9f8a3f8307ba] Establishing a connection 2016-07-27 05:38:50,837 WARN [hosebird-client-io-thread-0] com.twitter.hbc.httpclient.ClientBase GetTwitter[id=b2e83358-2e38-42c5-88a7-9f8a3f8307ba] Error connecting w/ status code - 420, reason - Enhance Your Calm 2016-07-27 05:39:07,949 ERROR [Timer-Driven Process Thread-2] o.a.nifi.processors.twitter.GetTwitter GetTwitter[id=b2e83358-2e38-42c5-88a7-9f8a3f8307ba] Received error HTTP_ERROR: HTTP/1.1 420 Enhance Your Calm. Will attempt to reconnect ... View more

thanks! had this same problem and getting ntpd running properly fixed it. ... View more

I got now(72,0) to work. don't know the ramifications.... ... View more

thanks! that's what I was trying to do but couldn't figure out the right syntax. ... View more