Member since
01-09-2017
33
Posts
0
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5804 | 03-22-2019 01:45 PM | |
1490 | 08-22-2018 03:00 PM | |
1228 | 03-12-2018 04:45 PM |
11-26-2018
05:29 PM
NO! if you are trying to escape input to generate a sql query you should never roll your own sanitization unless you fully trust the input. THIS IS VULNERABLE TO SQL INJECTION! You should be using the '?' parameter substitution in your putsql stage.
... View more
02-04-2019
09:56 AM
@David Miller Hi David, You are right with being carefull sending to many emails and that there will be situations where monitoring/errorhandling needs to be adjusted individual. But I want a standard process for the majority of always repeated occuring errors. You know, not reinventing the wheel every time again. And if one day my processes are designed further there won't be emails sent just logging everything and give the support some kind of graphical interface (dashboard) - that's the plan.
... View more
08-27-2018
07:53 PM
@David Miller For reference, the resource descriptors for the different component level access policies can be found in the NiFi Admin Guide, specifically: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#component-level-access-policies
... View more
06-02-2018
02:35 AM
David, I would recommend you create an SSLContextService at root which only uses the truststore and ask your users to select that controller service when necessary. If they have requirements to connect to external services which require mutual authentication via TLS client certificates, you may have to create additional controller services with limited keystore access and provide those on a per-instance/user basis. If these are globally-accessible external services (aka not organizationally-signed), you could also provide a generic controller service which uses the Java CA truststore (something like $JAVA_HOME/jre/lib/security/cacerts with default password "changeit").
... View more
05-29-2018
01:22 PM
@Henrik Olsen We completely understand how load-balanced redistribution of FlowFiles via a RPG is not the most elegant solution. There was consideration of separating input/output ports in to two different components (local and remote). In addition to the complexity with this, we also have to consider the backward compatibility. What impact with this have on NiFi users upgrading with flows developed with previous versions of NiFi. - Another option being looked at is adding the ability to enable load-balancing within the cluster directly on any connection. This would just be a new configuration option on existing connections with the default just behaving as connections do now. By enabling the load-balancing option, FlowFiles would be load-balanced across all connected nodes behind the scenes automatically. There are still technical hurdle here and no time table for this effort as of now. - Thank you, Matt
... View more
03-12-2018
04:45 PM
@MattClarke answered this question in https://community.hortonworks.com/questions/176292/how-to-configure-managed-ranger-authorizer-for-nif.html
... View more
11-27-2017
04:27 PM
I will accept the answer because it seems this might be an issue on my side. Thank you I will open up a ticket with hortonworks support if further troubleshooting is needed after I take a look at the logs. thanks again.
... View more
09-19-2017
01:49 PM
Thanks Matt, the pre-provisioned input port idea does seem workable.
... View more