Hi My one liner question: How can we ensure that the DatabaseTableSchemaRegistry recognizes changes in the table structure and updates the corresponding table schema definition? Details: Our PutDatabaseRecord processors' readers are configured to use the DatabaseTableSchemaRegistry to parse incoming JSON. We have observed multiple instances where the NiFi flow fails when the target table structure is altered, such as when columns are added or removed. When new columns are added to the target table, the PutDatabaseRecord reader does not recognize the change and continues to create insert statements without the new columns. We are unsure what may have resolved the issue, but in some instances, it was automatically resolved after a day. We suspect there may be an internal cache that is rebuilt periodically. We have no clear solution for this issue and would greatly appreciate any assistance regarding it. Our NiFi system is a 3-node cluster (version 2.1) that uses Kubernetes-based leader election and state management, without an external ZooKeeper. Thanks       ... View more

Hi I have a question on our Nifi flow design and specifically about the usage of DuplicateFlowFile processor. The latest documentation mentions that, it is intended for load test. Does that mean, it can not be used in regular production flows? Please confirm. https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/nifi-2.0.0-M4/org.apache.nifi.processors.standard.DuplicateFlowFile/index.html "Intended for load testing, this processor will create the configured number of copies of each incoming FlowFile."   Please verify the current and improved designs below and advise if any implications with the new approach (where DuplicateFlowFile processor is used to clone flow files) Current Design:     New Design is below (with DuplicateFlowFile processor)                 ... View more