Solr Push Endpoint Datasource and Configuration
The Solr Push Endpoint accepts documents and pushes them to Solr using the Fusion index pipelines.
In Fusion 3.0 and earlier, this is called the Push connector.
It uses the embedded JettySolrRunner to push the documents.
This requires defining a port for the JettySolrRunner that is not already in use by any other process.
The documents can then be sent to Fusion at that port, and they will be consumed by Fusion.
Property
Description
collection
Collection
Collection Name
type: string
commit_on_finish
Commit on Finish?
Issue a commit command when job is finished. Default is true.
type: boolean
default value: 'true'
port
required
datasource.port
type: integer
url
datasource.url
type: string
Initial Mappings
Description
mappings
Field Mappings
type: array of object
object attributes: {operation
: {stringcopy'
}source
(required)
: {stringtarget
: {string
unmapped
Unmapped fields mapping
type: object
object attributes: {operation
: {stringcopy'
}source
: {stringtarget
: {string
Property
Description
aliases
Process Aliases?
Keep track of original URI-s that resolved to the current URI. This negatively impacts performance and size of DB.
type: boolean
default value: 'false'
inlinks
Process Inlinks?
Keep track of incoming links. This negatively impacts performance and size of DB.
type: boolean
default value: 'false'
inv_aliases
Process Inverted Aliases?
Keep track of target URI-s that the current URI resolves to. This negatively impacts performance and size of DB.
type: boolean
default value: 'false'
type
Implementation Class Name
Fully qualified class name of ConnectorDb implementation.
type: string
default value: 'com.lucidworks.connectors.db.impl.MapDbConnectorDb'
minLength: 1
Property
Description
description Description
Optional description for datasource instance.
id Datasource ID
Unique name for datasource instance.
pipeline Pipeline ID
The index pipeline used to process documents.