Hello,
I have been running a single instance of NiFi server v1.7.1 on AWS behind ALB
and nginx:
ALB -> nginx -> NiFi
The configuration has been working fine, but since NiFi v1.8.0, I get Invalid
CORS request error when I try uploading a template file. Is there anything I
need to change in
Jim,
I had started to provide advice on configuring the logback.xml file when I
realized you want to output log messages directly to your own log file, not
using the provided log interface that ExecuteScript offers. I don’t know Python
well enough to be sure, but I get an error trying to
I clearly did not explain the existing situation well enough, so let me try
again.
I understand the desire to allow for variable substitution in the
keystore/truststore path properties. I think the misunderstanding stems from
what I was trying to point out in part 2 of my initial response.
I’ve run into another problem. I’m not sure if it’s related to the bug you’ve
created and referenced below, but it may be caused by my workaround to that bug
so I’m replying to the existing thread to provide full context.
The problem I’ve got now is an issue with programmatically enabling all
We are running NiFi 1.8, trying to log to a rotating log file from a python
script executed by an ExecuteScript processor. We are seeing no output to
the log file.
I seem to be establishing the log file handler and the logger without any
errors.
I see the log file in my log output directory, so I
Hello
The Apache NiFi team would like to announce the release of Apache NiFi
1.9.0.
In addition to more than 100 improvements and bug fixes, this release makes
integration with Apache Kudu and Impala a breeze. Provides stronger
integration with Google Big Query and Amazon Web Services. New
??I'm trying to set up a NiFi Cluster on AWS using ECS with External Zookeeper.
Have created a ECS Cluster for Zookeeper with 3 EC2 instance and running
zookeeper ensemble. This external Zookeeper is working fine as I tested with my
SolrCloud and also on my local NiFi. The local NiFi cluster
