Skip to main content
Connectors are components that act as bridges between your data and Fusion. They pull data from various sources and ingest it into Fusion for searching. Although connectors are not datasources, they work together for ingesting and indexing operations.

Connector

A connector fetches and processes data according to the datasource configuration.

Datasource

A datasource is a Fusion object that configures how connectors ingest data and routes that data through parsers, index pipelines, and into collections.
Connectors are built on the following platforms: Lucidworks provides a wide range of connectors, each specializing in a particular data type. There are connectors for databases, filesystems, repositories, social media, and more. To discover the right connector for you, see Find your connector.

Data ingestion process

Datasources

Fusion connects to your data

Connectors fetch data from your source systems based on the datasource configuration.

Data is processed according to your datasource configuration

The datasource configuration determines which parser stages and index pipeline stages process the ingested data.Parser stages transform raw data into structured documents with defined fields and values.Index pipeline stages prepare documents for search by normalizing values, enriching content, applying transformations, and filtering unwanted data.

Documents are indexed to a collection

Documents that complete the index pipeline are written to a collection where they become searchable.

Find your connector

Platforms

Pro

Pro connectors are V2 connectors that have been built to a notably high standard of quality, ensuring exceptional reliability and stability. They represent the premier tier of Fusion’s data integration platform, tested and validated to meet rigorous performance criteria. Lucidworks prioritizes development efforts to elevate V2 connectors to Pro status. When a connector achieves this quality threshold, the promotion is announced in the release notes.
Every Pro connector is a V2 connector, but not every V2 connector is a Pro connector.

V2

V2 connectors represent the current generation of Fusion’s data integration platform. They are built on a Java SDK framework and replace the deprecated V1 connector architecture.

Why V2 exists

The V2 platform addresses fundamental limitations in the original V1 connector design. V1 connectors were tightly coupled to Fusion releases, making updates slow and requiring full Fusion upgrades to get connector improvements. Security models mixed content and access controls together. Scaling required complex configuration rather than simply adding resources. V2 solves these problems. Connectors now update independently from Fusion itself, so you can deploy the latest plugin version without upgrading Fusion. Access controls are separated from content through standalone Security Access-control Lists (ACL). V2 also supports horizontal scaling, which lets you add more connector instances to work on the same job. The V2 platform also opens custom connector development through the Java SDK framework, giving you the tools to integrate any data source. For more information, see Build your own.

Technical architecture

The V2 platform is built on Google’s gRPC framework, a high-performance RPC system. gRPC provides HTTP/2 transport, protocol buffer serialization for efficient data handling, and support for bi-directional and multiplexed streams. This foundation enables the flexible service definitions, efficient communication, and distributed architecture that power the V2 platform.

Remote connectors

V2 connectors support two deployment models. Hosted connectors run inside the Fusion environment itself, with each node running independent connector instances. Remote connectors run outside Fusion as lightweight client processes that communicate back to the platform using efficient messaging. The remote model gives you deployment flexibility. Place connectors wherever your data lives, whether that’s for performance reasons, security requirements, or network access constraints. Learn more about remote deployment.

V1

V1 connectors are developed with a general-purpose crawler framework called Anda, created by Lucidworks. Anda helps simplify and streamline crawler development, reducing the task of developing a new crawler to gain access to your data. In Fusion 5, V1 connectors are included in the Fusion image.
In Fusion 5.9, all V1 connectors are deprecated. This means they are no longer being actively developed and will be removed in a future release.Some V1 connectors already have a direct replacement available. For other V1 connectors, a replacement is still under development. We will update the documentation when the replacement is available. See the connector reference page for details.We recommend migrating to the replacement connector as soon as possible to avoid any disruption to your workflows.For more information, see Deprecations and Removals.

Install and manage

Learn how to install, update, and manage V2 connectors in Fusion.
V1 connectors are pre-installed according to your Fusion version.

Install the latest version

  1. Navigate to Indexing > Datasources.
  2. Click Add.
  3. Select the connector from the list. It will install the latest version automatically.
It may take several minutes before the connector appears in the list of installed connectors.
This process always installs the latest version of the connector. Check the documentation for compatibility and release notes for key changes.
  1. Navigate to System > Blobs.
  2. Expand the Connector Plugin accordion.
  3. Select and delete the current connector version.
  4. Reinstall the connector using the instructions found in Install a Connector.
Lucidworks recommends you always use the latest version, but there may be cases where a specific version is preferred.
  1. Download the V2 connector Zip file.
  2. Navigate to System > Blobs.
  3. Expand the Connector Plugin accordion.
  4. Select and delete the current connector version.
  5. Click Add.
  6. Upload the Zip file containing the specific connector version.

Build your own

The Fusion Connectors SDK empowers developers to build custom connectors tailored to their specific data sources. While Fusion ships with a comprehensive library of pre-built connectors, the SDK enables you to create Java-based connectors that can integrate with proprietary systems, legacy databases, or any unique data repositories not covered by existing connectors. Using the SDK’s high-level interfaces and base classes, you can define custom configuration schemas, implement fetching logic, and leverage Fusion’s built-in features for state management, scheduling, and distributed processing without dealing directly with low-level gRPC code. You can develop locally, connect to a remote Fusion instance for testing, and then deploy the same artifact directly into Fusion for production use. To get started, refer to Connectors SDK.