@wann_douglas  That processor maintains state, it could be that you might have run it at one point. You can verify by right clicking on the processor and going to "view state" If there are values there then at one point it ran, and you probably want to clear the state.   To do so you can do that by clicking on "clear state" on the same place you viewed the state.   **** Make sure your processor is stopped.   Hope that helps. ... View more

That data seems like avro which is typically how the records are returned from a DB. You should send the FlowFile to a ConvertRecord processor and set it as an avro reader and an xml writer. This article has good information on how to do that. https://community.cloudera.com/t5/Community-Articles/XML-Record-Writer-in-Apache-NiFi-1-7-0/ta-p/248558 ... View more

Hi there is a state directory you should clear. Not sure exactly where it is on CM but it typically lives under $NIFI_HOMME/conf/state ( stop the NIFI's )   This is assuming you do not care about local state that processors might be using.   If you do then follow this: Can address it by going to $NIFI_HOME/state/local/partition-0.    Make sure NiFi is stopped. Rename whatever  .journal  file is there to  .journal.bak  (e.g.,  mv 158.journal 158.journal.bak ). Then copy this file to  /tmp  and in the  partition-0  directory use  cat 158.journal.bak /tmp/append-to-state > 158.journal  Start NiFi ... View more

Hi,   Sorry I don't get the question. This should work:   Ideally, I see it like this  "ExecuteSQL" →"PutFile"   Assuming based on comment you are getting a finished xml. ... View more

Hi,   could you expand on this?   For single table, we are using approx 40 processors. When we have less tables on the cluster, nifi works fine, whereas when we add more tables to the cluster, let's say, 150 tables which make total processor count to approx 6000 it becomes almost impossible to scale up the cluster.   What processor are you using to query your sql servers?   Have you increased the Max thread count on NIFI UI? ... View more

Hi are you using CM to manage your NIFI? Are the nodes here the zookeeper ensemble ( zookeeper cluster ) nifi.zookeeper.connect.string --> hostname1:2181,hostname2:2181,hostname3:2181 ... View more

Hi @rajivswe_2k7,   Alternatively, you can run your FlowFile through a ReplaceText processor and configuring it with replacement value of "ravi" / replacement strategy of "append" and Evaluation mode of "Line-by-line"   ... View more

Hello  @jdelarosa91,   First off welcome to Apache NIFI and its ecosystem.   You can accomplish this by using PutDistributedMapCache and FetchDistributedMapCache processors. First, you must configure the DistributedMapCacheServer and DistributedMapCacheClientService controller services. Then your dataflow should be like so:   Get token: InvokeHttp > UpdateAttribute ( Assign an attribute for instance MyToken and give it value TOKEN ) > EvaluateJsonPath ( get the value you want ) > PutDistributeMapCache ( For cache entry identifier give it the attribute ${MyToken}  )   Now in the MapCache we have a key, value like so: TOKEN / <the string you got from EvaluateJsonPath>   And when you need to grab the token:   GenerateFlowFile ( Configure an attribute MyToken give it value of TOKEN ) > FetchDistributeMapCache ( cache identifier ${MyToken} and "out identifier in attribute" give it a name to call your token with) > InvokeHttp ( Here when you need to use the token you can call it using nifi attribute ${the attribute with the token retrieved from you MapCache )     ... View more

Hi, What does the nifi-app.log say? bootstrap will show JVM related messages but for this case inspect your nifi.app.log,   ... View more

hmm to me it sounds like you have a DNS issue. I would go to the logs directory of one of the NIFI hosts: If using HDF it should be:   /usr/hdf/current/nifi/logs   and then do a grep like this:   grep "org.apache.nifi.web.server.JettyServer" *   One of the very last lines should have something that reads like so: nifi-app_2019-07-25_13.0.log:2019-07-25 13:30:40,076 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs: nifi-app_2019-07-25_13.0.log:2019-07-25 13:30:40,076 INFO [main] org.apache.nifi.web.server.JettyServer http://SOME-URL:SOME-PORT/nifi   Once you have that then I would try to ping that FQDN or IP and if you cant then you either have something going on with DNS or need to add that FQDN and IP to your local machines /etc/host file, assuming you are trying to reach the UI on a *NIX machine ... View more

Hi, Where is NIFI running? Is it on your own machine or somewhere else? By default and if using HDF, if NIFI is not secured it will run on port 9090 but if you are secured it will run on port 9091. Do you have a value on your machine in file /etc/hostname? on one of your nifi nodes?   I assume you are deploying HDF? ... View more