Member since
07-25-2016
55
Posts
28
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5903 | 07-26-2016 12:31 AM |
12-11-2023
08:35 AM
though i gave the permission to view user interface, i am still facing this issue.
... View more
09-08-2017
07:19 AM
Hi, New question added here: https://community.hortonworks.com/questions/135939/compare-attributes-of-different-flowfiles.html Hope you can help me. Jon
... View more
12-20-2016
02:49 PM
Monitor logs and REST API are good.
... View more
11-11-2016
07:32 PM
Thanks, that was very helpful,
... View more
11-21-2016
07:15 PM
2 Kudos
This is a bug, I have filed it under NIFI-3076. Workarounds might include changing the domain_id column to be signed (which is probably not desired), or using a cast() function to convert it into a data type (long, e.g.) that will be handled better for the time being. If you use a cast() or other function, you may want a column alias to ensure the column/field name is the one you want.
... View more
11-14-2016
03:48 PM
Nifi's provenance UI provides very low level information. If operations team is interested in high level information then other option is publish provenance information to ElasticSearch and create a Kibana dashboard on top of it customized for operations team.
... View more
11-09-2016
04:40 PM
1 Kudo
@Obaid Salikeen Unfortunately the answer is no at this time. NiFi has zookeeper as a dependency in HDF Ambari, so it is installed when the NiFi service is selected. Once NiFi is deployed there is nothing stopping you from updating the NiFi configs via Ambari to point at your existing Zookeeper you already have installed elsewhere. Keep in mind that other service within the HDF Ambari stack also rely on Zookeeper, so you may need to reconfigure them as well. Matt
... View more
11-07-2016
03:35 PM
2 Kudos
I am able to address this using the SplitContent processor. Check the config. below. It will split out two files one with Actual content you needed and second is the empty one. You can use update attribute processor to rename the files as per your requiremetns.
... View more
09-27-2017
06:26 PM
@Obaid Salikeen There is no direct correlation between CPU and heap memory usage. Heap usage is more processor and flow implementation specific. Processors that do things like splitting or merging of FlowFiles can end up using more heap. FlowFile Attributes live in heap memory. NiFi does swap FlowFile attribute to disk per connection based on FlowFile queue count. Default of 20,000 will trigger swapping to start on a connection. But there is no sap threshold based on FlowFile attribute map size. If a user creates large attribute values to FlowFile Attributes, that FlowFile heap usage is going to be higher. You see this isn scenarios where large parts of the FlowFile content is extracted to a FlowFile attribute. So when it comes to heap/memory usage, it comes down to flow design more then any correlation to the number of CPUs. Thanks, Matt
... View more