We have nearly wrapped up our testing with out Nifi scripts in dev, and are
now looking to push to QA. I found an article about creating a custom
properties file in order to specify each of your environmental specific
variables, and then specifying that file in nifi.properties at
Matt,
Thank you so much for your suggestion.But I would like to go with
executescript since I'm almost done with the code.I will try the processors
which you told in the future
I'm still stuck with some problem in my code.I have added it here
import java.io
from org.apache.commons.io import
Hey Mark,
Bryan beat me to it, I also believe that property has been deprecated. In
NiFiProperties.java, line 277, DEFAULT_REQUEST_REPLICATION_CLAIM_TIMEOUT is
flagged by IntelliJ as an unused field, as well.
On Tue, Nov 7, 2017 at 12:24 PM Bryan Bende wrote:
> Mark,
>
> I
Mark,
I believe that property is no longer used...
Grep'ing the source tree for it shows a few lingering references in
the admin guide and in src/test/resources, but nothing in regular
code.
It may be residual from the 0.x clustering model that was removed
during the 1.0.0 release.
-Bryan
On
It was observed that nifi.cluster.request.replication.claim.timeout
property is not in the default nifi.properties file. I assume this property
is still relevant (i.e. hasn't been deprecated.) Should it be included in
nifi.properties?
Thanks,
Mark
Tina,
I don't believe there are any processors right now that will count the number
of occurrences
of some string in a FlowFile. I would recommend either using an ExecuteScript
processor and
scripting it out in Groovy/Jython, or if you're comfortable enough with Java
and want to get your
hands