In Apache NiFi, what is a FlowFile?
Think about what moves inside NiFi between processors.
A FlowFile is the basic data packet in NiFi. It contains the actual data content and metadata attributes, allowing NiFi to track and route data through its flow.
What is the output of this NiFi Expression Language snippet if the attribute 'filename' is 'data_2024.csv'?
${filename:substring(5,9)}Substring(start, end) extracts characters from start index up to but not including end index.
The substring from index 5 to 9 in 'data_2024.csv' is '2024'. Indexing starts at 0.
You run a NiFi Data Provenance query filtering events by a specific processor and time range. The query returns 3 events. What does this output represent?
Data Provenance tracks FlowFile events like creation, modification, and transfer.
The query output shows FlowFile events processed by the selected processor during the specified time.
Given this NiFi processor configuration snippet, which option explains why the processor fails to start?
Properties: Input Directory: /data/input File Filter: *.csv Scheduling Strategy: Timer-driven Run Schedule: 0 sec
Check if the run schedule value is valid for timer-driven scheduling.
Run Schedule cannot be zero seconds; it must be a positive number to schedule processor runs.
You need to design a NiFi flow that reads streaming data from Kafka, filters records where 'status' equals 'error', and writes them to HDFS. Which sequence of processors correctly implements this?
Consider processors that can consume Kafka and filter records by content.
ConsumeKafka reads streaming data, QueryRecord filters records by field values, and PutHDFS writes filtered data to HDFS.