Apache Flume pipelines should be implemented using Apache NiFi components
Please consider using one the following alternatives: No alternative components suggested.
Execute a Flume source. Each Flume Event is sent to the success relationship as a FlowFile
flume, hadoop, get, source
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 |
|---|---|---|---|---|
| Source Type | Source Type | The component type name for the source. For some sources, this is a short, symbolic name (e.g. spooldir). For others, it's the fully-qualified name of the Source class. See the Flume User Guide for details. | ||
| Agent Name | Agent Name | tier1 | The name of the agent used in the Flume source configuration | |
| Source Name | Source Name | src-1 | The name of the source used in the Flume source configuration | |
| Flume Configuration | Flume Configuration | The Flume configuration for the source copied from the flume.properties file |
| Name | Description |
|---|---|
| success |
| Required Permission | Explanation |
|---|---|
| execute code | Provides operator the ability to execute arbitrary Flume configurations assuming all permissions that NiFi has. |