Member since
06-26-2015
505
Posts
129
Kudos Received
114
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
833 | 09-20-2022 03:33 PM | |
2633 | 09-19-2022 04:47 PM | |
1508 | 09-11-2022 05:01 PM | |
1632 | 09-06-2022 02:23 PM | |
2473 | 09-06-2022 04:30 AM |
06-22-2022
04:13 PM
1 Kudo
@nada , Please check this solution: https://community.cloudera.com/t5/Community-Articles/Decompressing-nested-ZIP-files-in-NiFi/ta-p/346169 Cheers, André
... View more
06-22-2022
04:12 PM
2 Kudos
This has been a recurring question in the Community forum. I replied to those a few times so I've decided to post the answer here as an article so that's easier to find and reference. The question is: if you have a ZIP file that contains other ZIP files (which may in turn contain other ZIP files, etc.), how can I extract all the ZIP files, recursively, using NiFi? One way to do that is to implement the following data flow: The RouteOnAttribute processor checks the file name and if it's a ZIP file it sends it for unpacking. Otherwise sends the non-zip file downstream. You can find the flow definition attached below. HTH, André
... View more
Labels:
06-22-2022
03:55 PM
@Arqui , Are you running your nginx externally? How are you trying to connect? Cheers, André
... View more
06-13-2022
05:10 PM
1 Kudo
Hi, @Arqui , I've made a few changes to your docker-compose.yml file to automatically generate certificates and set credentials. Please check it out here. You don't need to provide or configure anything manually. Just start the docker composer, connect to https://localhost:8443/nifi and authenticate with admin/supersecret1 (you can change username and password in the compose configuration. Cheers, André
... View more
06-08-2022
11:34 PM
@Arqui , Your initial admin should be simply: INITIAL_ADMIN_IDENTITY: "my_admin" Cheers, André
... View more
06-08-2022
08:26 PM
@dfdf , In Cloudera Manager, please go to SQL Stream Builder > Configuration and check that the below property is set correctly: If it's not set to the /usr/share/python3 directory, please set it to that, save and restart the service. Cheers, André
... View more
06-08-2022
08:16 PM
@nada , Could you share a sample of the InvokeHTTP response and also the flow that you currently have? Cheers, André
... View more
06-08-2022
08:08 PM
@migu , What's your NiFi version and what's your JOLT transformation? This should work, provided that your JOLTed JSON is correct. Please see the attached flow, which works fine for me. Cheers, André
... View more
06-08-2022
06:04 PM
1 Kudo
@benjbenj Would using a different type of transport be an option in your case? Instead of using S2S you could possibly use a pair InvokeHTTP and ListenHTTP to send the data in a port that you can specify. The port wouldn't necessarily have to change between minifi instances, but you could also parameterize it if needed. Cheers, André
... View more
05-19-2022
08:14 PM
@SAMSAL , Here's what I think is happening: Your user, who has id "168b019c-0180-1000-ffff-fffffbf36c3a" (from users.xml) only has access to the processor group with id "155cec02-0180-1000-6d4b-ac96d2372f41". For authorizations.xml: <policy identifier="168b74d6-0180-1000-ffff-ffffd79ba94d" resource="/process-groups/155cec02-0180-1000-6d4b-ac96d2372f41" action="R">
<group identifier="1966f436-0180-1000-ffff-ffffd1d17786"/>
<user identifier="168b019c-0180-1000-ffff-fffffbf36c3a"/>
</policy>
<policy identifier="168bae4a-0180-1000-ffff-ffff98c1495b" resource="/process-groups/155cec02-0180-1000-6d4b-ac96d2372f41" action="W">
<group identifier="1966f436-0180-1000-ffff-ffffd1d17786"/>
<user identifier="168b019c-0180-1000-ffff-fffffbf36c3a"/>
</policy> Your PUT command is referencing a processor with id "385fcdc0-0180-1000-0000-000030a768e3". I don't know how your canvas is organized, but my guess is that this processor does not belong inside the processor group "155cec02-0180-1000-6d4b-ac96d2372f41" and because of that the user is being denied access (403 Forbidden). To solve that you can login to the UI using an admin user, right-click on the Process Group that contains the processor that you're trying to manipulate and click on "Manage access policies". In the Access Policies page, add your user to the "view the component" and "modify the component" policies. After that, try again. Cheers, André
... View more