title: Using NiFi for scheduling Hadoop batch processes
body: <p>According to <a href="https://nifi.apache.org/" rel="nofollow noreferrer">NiFi's homepage</a>, it "supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic".</p>
  
  <p>I've been playing with NiFi in the last couple of months and can't help wondering why not using it also for scheduling batch processes.</p>
  
  <p>Let's say I have a <b>use case</b> in which data flows into Hadoop, processed by a series of Hive \ MapReduce jobs, then exported to some external NoSql database to be used by some system.</p>
  
  <p>Using NiFi in order to ingest and flow data into Hadoop is a use case that NiFi was built for.<br>
  However, using Nifi in order to schedule the jobs on Hadoop ("Oozie-like") is a use case I haven't encountered others implementing, and since it seems completely possible to implement, I'm trying to understand if there are reasons not to do so.</p>
  
  <p>The gains of doing it all on NiFi is that one will get a visual representation of the entire course of data, from source to destination in one place. In case of complicated flows it is very important for maintenance.</p>
  
  <p>In other words - my question is: <b>Are there reasons not to use NiFi as a scheduler\coordinator for batch processes</b>? If so - what problems may arise in such a use case?</p>
  
  <hr>
  
  <p>PS - I've read this: "<a href="https://stackoverflow.com/questions/41607235/is-nifi-having-batch-processing">Is Nifi having batch processing?</a>" - but my question aims to a different sense of "batch processing in NiFi" than the one raised in the attached question</p>