Adam,
This probably isn’t easily accomplished. You might be able to deploy with an
“accept all” truststore so that any certificate is accepted, and provide a
keystore that doesn’t have a private key to try and satisfy the properties
loading without actually enabling HTTPS security on NiFi and
Hello all,
We have NiFi Registry 0.2.0 spun up with an nginx proxy and SSL termination
such that our services is being served over https without using NiFi’s builtin
security configurations.
We are able to add the registry service to NiFi using our HTTPS endpoint and
everything works
Hi Jon. Just wanted to say that I have developed this ReportingTask since
we had a similar issue to yours, only we had to report metrics to graphite.
We are currently using it in production.
I tried to implement as generic design as possible, so reporting to other
endpoints (e.g. cloudwatch)
You should be able to make your own NAR with two modules like:
nifi-cloudwatch-metrics - contains your service implementation with a
provided dependency on nifi-metrics-reporter-service-api
nifi-cloudwatch-metrics-nar - packages your implementation and has a
NAR dependency on
We were planning on having a reporter to pipe the metrics off to AWS
CloudWatch. The one issue being ran into -- and we've ran into it for other
components -- is the classloading. What is the recommended way of adding
alternate implementations of services (in this case MetricReporterService)?
We
Dev Team,
I don’t think we've reached a conclusion on this discussion, but would like
too. I had not done enough research when I originally suggested this as a, "New
Pattern". Having done a bit more research now, I'd say this is already a well
established pattern.
Examples using this pattern
Joe,
The new authorizations should not impact the availability of the Global
Menu. And, your second suggestion was spot on. I did a hard refresh and
that cleared it up.
Thanks!
-Mark
On Fri, Nov 2, 2018 at 12:57 PM Joe Witt wrote:
> Mark,
>
> I *think* there are new authorizations you'd need
Mark,
I *think* there are new authorizations you'd need to give yourself in
that case. Have you already looked there?
And finally, hard refresh to clear cache is also a possible path
Thanks
On Fri, Nov 2, 2018 at 12:26 PM Mark Bean wrote:
>
> I attempted to upgrade a 3-node Cluster from 1.6.0
I attempted to upgrade a 3-node Cluster from 1.6.0 to 1.8.0. The process I
used was to configure 1.8.0 on all Nodes. Then, one Node at a time,
shutdown the 1.6.0 and startup the 1.8.0 version. For the first Node, I
copied the flow.xml.gz from the previous 1.6.0 installation. (The
I have a (Kerberos) secured NIFI running and it is connecting to secured SASL
secured zookeeper. Zookeeper-jaas is configured in bootstrap. Cluster starts
clean
Not sure, if there is something else need to be done.
Configuratons are as below:
conf/state-management.xml
I have a working relationship between a controller service and a processor,
but the processor uses a user-supplied Groovy script to massage some data.
The ScriptEngine is used to make a CompiledScript. I then have a pattern
that looks like this:
@Override
public void
11 matches
Mail list logo
