Member since
07-30-2019
3396
Posts
1619
Kudos Received
1001
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 419 | 11-05-2025 11:01 AM | |
| 317 | 11-05-2025 08:01 AM | |
| 456 | 11-04-2025 10:16 AM | |
| 672 | 10-20-2025 06:29 AM | |
| 812 | 10-10-2025 08:03 AM |
05-25-2017
02:22 PM
Please take a look at @Matt Clarke's response above on how to extract csv files only. It is the most straight forward way.
... View more
05-24-2017
01:52 PM
@Bhushan Babar Glad i was able to help resolve your issue. Could you please click "accept" the answer i provided to close out this question in the community? Thank you,
Matt
... View more
05-24-2017
12:06 PM
@regie canada The extractText processor creates FlowFile attributes from the extracted text. NiFi has an AttributesToJSON processor you can use to generate JSON form these created attributes. For new questions, please open a new question. It makes it easier for community users to search for answers. Thanks, Matt
... View more
05-19-2017
08:17 AM
@Matt Clarke Thank you very very much, your answer was very useful for me
... View more
05-15-2017
05:27 PM
@Muhammad Umar When NiFi starts and has not been configured with a specific hostname or IP in the (nifi.web.http.host=) in the nifi.properties file, it looks to bind to the IP address registered to every NIC card present on the host system. If you try to specify a hostname or IP that does not resolve or match the IP registered to any of your NIC cards, NiFi will fail to start. NiFi can not bind to a port that belongs to an IP it does not own.
You can run the "ifconfig" command on the host running NiFi to see all NICs and the IP registered to them. You should see the 172.17.x.x address and not the 192.168.x.x address shown. It definitely sounds like there is some network address translation going on here. The fact that you can reach NiFi over http://192.68.x.x:8078// confirms this. It is simply routing all traffic from the 192.169.x.x address to the internal 172.17.x.x address. We confirmed already your browser cannot resolve a path directly to 172.17.x.x, because if you could, NiFi's UI would have opened. NiFi is in fact bound to 172.17.x.x and not 192.168.x.x. NiFi cannot control how traffic is being routed to this endpoint by the network. Thanks, Matt
... View more
02-18-2018
04:47 PM
In my understanding, everything is based anyhow on "processGroup". and there is a "root" process group that is shared among all the users. It would be nice to allow the creation of multiple "root" process group and define for a user or a group of user what is the root "processGroup". Of course, super users or users belonging to different groups, should have the possibilty to see the list of root "processGroup" they can access and enter it. what do you think? for real multi-tenancy this would be quite interesting.
... View more
05-21-2017
10:15 AM
@Wynner I resolved my issue because in fact i have 3 environments, and i was ponting the listProcessor to the wrong environment. I have my local file system Windows 8.1, with VirtualBox, running CentOS 7, and on top of CentOS i have the sandbox, and i was pointing my folder to the CentOS layer. My /media/sf_SharedFolder was placed in CentOS and not in sandbox.
I have to thank you for your help.
... View more
05-17-2017
03:16 PM
@Muhammad Umar Did changing to absolute paths resolve your issue here? If so, please mark answer as accepted. Thank you, Matt
... View more
06-06-2017
09:02 PM
@Alvin Jin My suggestion would be use something like: https://regex101.com/ You can enter your regex and sample test you want to run it against. Matt
... View more
05-10-2017
12:47 PM
Based on what you provided above it looks like you installed via the nifi tar.gz file. By default NiFi runs unsecure on port 8080. So yes, you want to change that port to some unused port on your server. Thanks,
Matt
... View more