Connect processors into a bounded dataflow, start them for a controlled test and inspect the provenance record. Stop the processors after the test and keep ongoing execution as a separate decision. Review file-removal behaviour before using GetFile.12
Add processors to the canvas and inspect their documented behaviour.2
Run a synthetic two-processor test flow and inspect data provenance.32
Get started
Use the synthetic GenerateFlowFile and LogAttribute example with a five-second interval and 10 KB files. Start it for a bounded test, inspect provenance, stop it and wait for active tasks to finish.32
Ways to use it
Ideas based on documented features.
Test a small data-movement flow with copied inputs and an inspectable provenance record.12
Before you start
Stopping prevents new tasks; let active work finish. GetFile removes ingested local files, so use synthetic data or disposable copies for testing and match the guide to the installed version.32