Apache Flume pipelines should be implemented using Apache NiFi components
Please consider using one the following alternatives: No alternative components suggested.
Execute a Flume sink. Each input FlowFile is converted into a Flume Event for processing by the sink.
flume, hadoop, put, sink
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Sink Type | Sink Type | The component type name for the sink. For some sinks, this is a short, symbolic name (e.g. hdfs). For others, it's the fully-qualified name of the Sink class. See the Flume User Guide for details. | ||
| Agent Name | Agent Name | tier1 | The name of the agent used in the Flume sink configuration | |
| Sink Name | Sink Name | sink-1 | The name of the sink used in the Flume sink configuration | |
| Flume Configuration | Flume Configuration | The Flume configuration for the sink copied from the flume.properties file |
| Name | Description |
|---|---|
| success | |
| failure |
| Required Permission | Explanation |
|---|---|
| execute code | Provides operator the ability to execute arbitrary Flume configurations assuming all permissions that NiFi has. |