Connector Configuration Parameters

This section describes the configuration parameters that you can use to configure the connector. Connectors usually require you to configure the connection to the data repository, and additional parameters are usually provided so that you can select the data to ingest and ignore unwanted items.

NiFi Connectors

To configure a connector that you have deployed in Apache NiFi, set these parameters in the processor configuration dialog (right-click the processor and click Configure).

NiFi Ingest provides separate processors for each supported connector action. For example, if you deploy a File System Connector:

  • The GetFileSystem processor performs the synchronize action, which gets the latest changes from the data repository. You might use a "Get" processor to keep your Knowledge Discovery index up-to-date.
  • The ViewFileSystem processor performs the view action, which retrieves a file from the data repository so that a user can view it.
  • The DeleteFileSystem processor performs the delete action, which deletes a file from the data repository.

Each processor is likely to support a subset of the configuration parameters. Some of the parameters might apply to every action, but others might apply to just one.

ACI Connectors

To configure a connector that you have deployed as a stand-alone ACI server, set these parameters in the connector's configuration file, in a section that is named in the [FetchTasks] section, by the N parameter. For example:

[FetchTasks]
0=MyTask

[MyTask]
// Connector Configuration Parameters

Some parameters can be set in more than one section of the configuration file. If a parameter is set in more than one section, the value of the parameter located in the most specific section overrides the value of the parameter defined in the other sections. For example, if a parameter can be set in "TaskName or FetchTasks or Default", the value in the TaskName section overrides the value in the FetchTasks section, which in turn overrides the value in the Default section. This means that you can set a default value for a parameter, and then override that value for specific tasks.

This document lists the configuration sections from most specific to least specific.