Hi, what are the recommended approaches for handling the following scenario? NiFi is ingesting lots of files (say, pull from a remote system into the flow), and we care about file as a whole only, so flowfile content is the file, no further splits or row-by-row processing. The size of files can vary from few MBs to GBs, which is not the problem, but what happens when there are millions of files ingested this way? Say, they end up in HDFS in the dataflow. Given that file content will be recorded in the content repository to enable data provenance, disk space may become an issue. Any way to control this purge/expiration on a more fine-grained level other than instance-wide journal settings? ... View more

Hi All, The use case is a Banana dashboard working with a SolrCloud instance/cluster. If we follow default steps we end up using the 'data_driven_schema' in Solr, which makes it easy for it to accept any random data and try index it. However, the problem is down the line. Banana table widget can't sort on many columns as Solr complains about those fields being multi-valued. In fact, they are not, and unique (checked via admin section), but rather declared multi-valued. What is the approach to address this? Ideally, without having to specify a complete new schema for a Solr index. Can one have a benefit of flexible fields, but default to non-multi-valued maybe? ... View more

Hi, I'd like to understand how the receiving end of the site-to-site protocol works. The sending side drops a remote process group on the canvas and is mostly done. The receiving side - simple in case of a single NiFi node. In a cluster, though, we still need to specify a FQDN to connect to. What is the best practice there? If we put a load balancer in front, would it break batch affinity (when site2site batches sends for you)? ... View more