Member since
07-30-2019
3436
Posts
1632
Kudos Received
1012
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 129 | 01-27-2026 12:46 PM | |
| 556 | 01-13-2026 11:14 AM | |
| 1194 | 01-09-2026 06:58 AM | |
| 989 | 12-17-2025 05:55 AM | |
| 491 | 12-17-2025 05:34 AM |
10-04-2021
10:04 AM
@JelenaS Making a bucket public only only control whether an unauthenticated and authorized user can import flows from a bucket on to the NiFi instance. So ONLY make it public if you want anonymous users to be able to use your version controlled flows in that bucket. Users must still be authenticated and authorized in order to commit new flows to a public bucket. As far as the global polices you set up for your "CN=<domainname>.net, OU=NiFi", that looks correct (don't need "write" on buckets), but is only correct if that string matches exactly what is coming from the certificates used on your secured NiFi instance(s) post and identity mapping happening on the NiFi-Registry server. So check your nifi-registry.properties file for any configured Identity Mapping Properties: https://nifi.apache.org/docs/nifi-registry-docs/html/administration-guide.html#identity-mapping-properties For example: nifi.registry.security.identity.mapping.pattern.dn=^CN=(.*?), OU=(.*?)$
nifi.registry.security.identity.mapping.value.dn=$1
nifi.registry.security.identity.mapping.transform.dn=NONE with above and "CN=<domainname>.net, OU=NiFi", the string that would get checked for authorization in NiFi-Registry would be only "<domainname>.net" and thus be the string that would need to be authorized in instead of the full DN. When you are authenticated in to your NiFi instance as your nifi_admin user, what exact string is displayed in the upper right corner of the NiFi UI? Is it "nifi_admin" or "CN=nifi_admin, OU=NiFi" because whatever displayed there is going to be the exact user string that gets proxied to the NiFi-Registry. Also keep in mind that USER/CLIENT strings are case sensitive in both NIFi and NiFi-Registry. Mapping transforms can be used to convert strings to all uppercase (UPPER) or all lowercase (LOWER). Hope this helps, Matt
... View more
10-03-2021
10:32 PM
Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.
... View more
09-30-2021
02:03 PM
Thanks @MattWho for the quick response. I can see the active thread in the top right corner of the processor which is hang forever. The max timer driven threads are not consumed, i will try to get the thread dump and see. I think i should contact provider of the processor (marklogic) as you suggested. Thank you.
... View more
09-30-2021
01:39 PM
1 Kudo
@VagnerBelfort From your example, it appears you are looking to modify only the first line of your input file and your modification seems pretty simple. In that case, one possible solution is simply to use the ReplaceText processor to modify that first line to match you new modified structure. Here is a ReplaceText processor configuration I used to accomplish your desired output: Search Value (Java regular Expression): ^"(.*?)":"(.*?)":(.*?)\{ Above contains 3 capture groups to capture the unique parts of your input we want to reuse. Replacement Value: {
"hash":"$1:$2:$3", Make note of the added line return. All characters are literals except the $1, $2, and $3 which get replaced with the string form each of the three capture groups from the Java Regex. Replacement Strategy: Regex Replace Evaluation Mode: Line-by-Line Line-by-Line Evaluation Mode: First-Line If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt
... View more
09-30-2021
06:10 AM
2 Kudos
@DSan You run in to some unique challenges with your specific use case since the properties you want to enable NEL expect Java regular expressions. The reserved characters that would tell NiFi that a NEL statement is being used are special characters in Java Regular expressions. You may want to raise your change/improvement request as a Jira in the Apache NiFi Jira project: https://issues.apache.org/jira/browse/NIFI There may be others in the community that like this idea and have suggestions for working around the challenge I shared above. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt
... View more
09-28-2021
12:21 AM
I understand and got the solution to this problem then thank you for your help. Thanks MattWho.
... View more
09-27-2021
10:57 AM
1 Kudo
@paygb You are absolutely correct, the Cloudera Manager configuration property within NiFi configurations fro logback.xml does require you to input the entire logbck.xml and then add your modifications. Adding a new logger for the ControllerStatusReportingTask would require adding a logger like this: <logger name="org.apache.nifi.controller.ControllerStatusReportingTask" level="DEBUG"/> You can add this logger in line along with other loggers already in the logback.xml The result would be all logging from this class at a DEBUG level and below would go in to the nifi-app.log. You could optionally add an additional appender (NiFi has three existing appender now for the nifi-app.log, nifi-user.log and nifi-bootstrap.log files). You can copy and modify one of those and the your logger would need to look like this: <logger name="org.apache.nifi.controller.ControllerStatusReportingTask" level="DEBUG" additivity="false">
<appender-ref ref="NEW_APPENDER"/>
</logger> If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt
... View more
09-25-2021
11:52 PM
Hey Matt, Thanks for you advise. I have followed the below approach and worked fine for my issue. Thanks for your help. ${absolute.path:getDelimitedField('5','/')}
... View more
09-24-2021
10:48 AM
@samarsimha The zookeeper client version used in Apache NiFi versions prior to 1.13 do not support TLS. You'll need to upgrade your NiFi 1.13 from 1.10 to take advantage of the new TLS connectivity to Zookeeper. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt
... View more
09-24-2021
09:45 AM
@nitinchauhan Sharing details around your dataflow, processor being used, etc... may help in getting engagement from the community. The output you shared shows a failed connection to the a NiFI rest-api endpoint (/nifi-api/system-diagnostics) because of connection refused. Details on this processors configurations? What is seen in the logs of the target NiFi which this processor is trying to connect with? Thanks, Matt
... View more