Hi Will, On a logical point of view, you are right, I think there is no absolute need to have an incoming connection. As it is coded right now, it requires an incoming connection to allow users to leverage the expression language in the properties of the processor. However I think that the incoming connection could be optional instead of required. The simplest way to get things working is to add a GenerateFlowFile processor before the FetchElasticsearch one. You can configure the generate flow file processor with a 0B size to have empty flow files, and change the scheduling as cron-time based to decide the frequency of the requests that will be sent to Elasticsearch. Hope that helps. ... View more

Hi Wellington, There are few examples out there to use the Twitter API with Storm. You should have a look to Hortonworks tutorials (like this one http://hortonworks.com/hadoop-tutorial/ingesting-processing-real-time-events-apache-storm/) to have explained and comprehensive examples using the sandbox. If you only want simple code examples, you will find a lot by searching for "github twitter storm" on the internet. A possible example is: https://github.com/pvillard31/storm-twitter But there are a lot of possibilities depending on how you want to use the Twitter API. For example, you will find some examples that leverages the Trident API in Storm. Hope that helps! ... View more

Hi Pradeep, NiFi is running on Windows. As far as I know, I don't see any reason why this tutorial wouldn't work on Windows Azure. ... View more