Member since
09-23-2015
88
Posts
109
Kudos Received
1
Solution
04-22-2026
04:37 AM
This is a really clean and practical walkthrough—streaming data into Hive using NiFi’s HiveStreaming makes the whole process feel effortless, especially for beginners who want results without diving into heavy coding. I like how it simplifies handling large historical datasets like the Olympics records, turning raw CSV files into instantly usable insights. It actually reminds me of how platforms like Sportzfy deliver content smoothly behind the scenes—efficient pipelines make all the difference.
... View more
03-17-2016
10:06 PM
1 Kudo
Please find below a potential design for Disk & RAID configuration for a typical 12 disk Server running NiFi. This design is intended for a simple log ingestion use case, where customer needs very little provenance records, but would also like reliability on the storage layer. FlowFile repo: 2 drives setup as RAID 1
Provenance repo: 2 Drives RAID 1 Content repo setup either:
4 drives (RAID 10) /cont_repo1
4 drives (RAID 10) /cont_repo2
or
2 drives (RAID 1) /cont_repo1
2 drives (RAID 1) /cont_repo2
2 drives (RAID 1) /cont_repo3
2 drives (RAID 1) /cont_repo4 Thanks @mpayne & @Andrew Grande for guidance!
... View more
Labels:
02-24-2017
08:40 PM
Great article Wes!
... View more
01-11-2016
08:40 PM
By Default NiFi will run as what ever user starts NiFi.
NiFi can however be configured to start as a specific user by setting the run.as= property inside the bootstrap.conf file.
*** Note that the user configured in this property will need to have sudo privileges to the java executable on linux based deployments. This could interfere with some processors that are dependent on the java process being owned by a particular user since it will be owned by root. *** Setting the run.as user allows you to setup NiFi as a service that can be configured to start as part of the OS starting.
... View more