Sounds like the output of a MapReduce job that you ran. HBase does not store anything outside of the value of "hbase.rootdir" in hbase-site.xml. On HDP, this defaults to "/apps/hbase/data". As long as you have no changed this configuration property, you can rest assured that HBase is not actively referring to files stored in "/tmp". ... View more

Hi @srini, One way to do it is to use the MonitorActivity processor that can emit a flow file if there is no activity since X minutes. This generated flow file can then be routed to a processor sending emails. Hope this helps. ... View more

Hi @srini, NiFi does support the addition of custom transformations which can be referenced with a "drop in" jar. You could create your own transformation class, which extends the jolt library, that provides the functionality you need and be available to NiFi on the file system. Given that this is a new function in a later version of Jolt I would be careful using that the as a custom jar; that may cause a conflict but I haven't tested this myself to be sure. Below are some use cases on how to apply custom functions in NiFi Case 1 – Custom Transform Selected In this case if the Custom option of Transform is selected then 1) a Custom Transform Class Name should be entered and 2) one or more module paths should be provided. The Custom Transform Class Name should be a fully qualified classname (e.g. eu.zacheusz.jolt.date.Dater). The Module Path can take a comma delimited list of directory locations or one or more jar files. Once these fields are populated the Advanced view will support validation and saving of the specification. A user can switch between transformation types in the UI but not custom class names & module paths. Case 2 – Chain Transformation Selected with Custom Transformations embedded In this case if you wants to use one or more transforms (that include custom transformations) in your specification then the Chainr spec option can be used with one or more module path provides. In this case the Custom Transform Class Name property is not required and would be ignored (since one or more custom transformations could be invoked in the spec). As in Case 1 the Advanced view will support validation and saving of specification if the required fields are populated for this case. I hope this helps! Please let me know if you have any questions. ... View more