File Upload V1

The File Upload V1 connector provides a convenient way to quickly ingest data from a single uploaded file. It can crawl exactly one file from Fusion’s Blob Store and feed it through an index pipeline.

Compatible with Fusion version: 4.0.0 through 5.12.0

V1 deprecation and removal notice

All V1 connectors are deprecated in Fusion 5.18.0 and later. This means they are no longer being actively developed and will be removed in Fusion 6. V1 connectors were also previously deprecated in Fusion 5.12.0 but remained available in all versions between 5.12.0 and 5.18.0, including the Fusion 5.9.x long-term support release line, to support customers on those versions.

The replacement for this connector is the File Upload Pro connector.

If you are using this connector, you must migrate to the replacement connector or a supported alternative before upgrading to Fusion 6. Migrate to the replacement connector as soon as possible to avoid any disruption to your workflows.

Prerequisites

Perform these prerequisites to ensure the connector can reliably access, crawl, and index your data. Proper setup helps avoid configuration or permission errors, so use the following guidelines to keep your content available for discovery and search in Fusion.

1. Install the connector plugin. Create a File Upload (V1) datasource under Indexing > Datasources > Add+ > File Upload.
2. You must have a file uploaded to Fusion’s Blob Store using one of the following methods:
   1. Upload through System > Blobs > Add > Upload File. Note the file ID, as this is entered in the connector’s File ID field when setting up the connector.
   2. Upload the file when adding the connector as a datasource by selecting it through Choose File under FILE UPLOAD. This automatically populates the file ID field using the name of the file.

Authentication

The File Upload V1 connector does not require any external HTTP or token-based authentication. You use a fileId that is already uploaded to the Blob Store, and Fusion ingests it directly.

Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.