{formatDescription(description)}
} {visibleProps.map(([name, prop]) => { const isRequired = requiredProps.includes(name); const hasDefault = prop.default !== undefined; const rawDefault = prop.default; const isComplexDefault = hasDefault && (typeof rawDefault === "object" || typeof rawDefault === "string" && (rawDefault.length > 20 || rawDefault.includes('"'))); const fieldProps = { key: name, body: prop.title || name, type: prop.type, ...prop.title && ({ post: [<>API property: {name}] }), ...isRequired && ({ required: true }), ...!isComplexDefault && hasDefault ? { default: sanitize(String(rawDefault)) } : {} }; const isObject = prop.type === "object" && prop.properties; const isArrayOfObjects = prop.type === "array" && prop.items?.type === "object" && prop.items.properties; return{formatDescription(prop.description)}
} {isComplexDefault &&Default:
{JSON.stringify(rawDefault, null, 2)}
Object attributes:
{'{\n'}
{Object.entries(prop.items.properties).map(([iname, iprop]) => <>
{` ${iname}`}
{prop.items?.required?.includes(iname) && required}
{`: {\n display name: ${sanitize(iprop.title || '')}\n type: ${iprop.type}\n }\n`}
)}
{'}'}
To transform data after it leaves the Solr Pro connector, use the Index Pipeline stages.
## Migrate from the Solr V1 connector
We strongly encourage migrating from the Solr V1 connector to the Solr Pro connector. If you are currently using the [Solr V1 connector](/docs/fusion-connectors/connectors/v1/solr) and want to migrate your existing connector settings, consult the [general migration guide](/docs/fusion-connectors/migration-guide) and the [Solr-specific migration guide](/docs/fusion-connectors/migration-solr-pro) in the Migration Guide series for instructions.
## Prerequisites
Before using the Solr Pro connector, ensure that you are using Solr 8 or later or later for your Solr environment. Your Fusion environment must be using Fusion 5.9.0 or later.
### Confirm Solr availability
You need to have an accessible external standalone Apache Solr or SolrCloud deployment, as Fusion must be able to reach Solr over HTTP/S. For SolrCloud, make sure the Solr Node endpoint is reachable from Fusion and not just Zookeeper.
The connector uses Solr's `/select` endpoint to pull documents. Ensure `/select` is enabled and not blocked by security rules or proxies.
The Solr instance should return standard `response.docs` JSON.
* For incremental crawling, enable delta indexing.
* Solr documents must include a timestamp field such as `last_modified` with a format of ISO-8601 or Solr-readable datetime.
* Example: `"timestampField": "last_modified"`
* To enforce document-level security, your Solr docs must include user/group fields mapped to Fusion's access control list (ACL) fields like `_lw_acl_read`.
### Write valid queries
You must have a valid Solr query to extract data. When writing queries or filter query, the prefixes of `q` and `fq` are already appended.
* For queries, use `*:*` to fetch all documents.
* You can use filters such as `type:product`.
* Test your query in the Solr Admin UI before using it in your datasource settings.
To use field mapping, know which Solr fields to extract:
* Unique ID field such as `id`
* Optional timestamp field for incremental crawl
* Any custom metadata fields
The Solr Pro connector validates queries before you start a job by executing the query against your Solr environment in a controlled way. If the query generates an error from the server in the validation process, the connector includes detailed and actionable error messages so you can identify and fix errors quickly.
## Authentication
Currently, the Solr Pro connector supports connections to unencrypted, public Solr endpoints, so no authentication is needed.
## Troubleshooting
This section outlines some common troubleshooting topics.
### Query timeout exceeded
If you consistently see the "Query timeout exceeded" error in the Solr connector, your query timeout is likely too low. Increase the **Query Timeout** value or reduce the **Batch Size** so the connector can process a batch in a timely manner.
### Cursor mark not supported
If the Solr connector returns the "Cursor mark not supported" error, you are using a Solr environment earlier than Solr 4.7. Cursor mark pagination is not supported in Solr versions earlier than Solr 4.7. Set **Use cursor mark** to false, and the Solr connector will use offset pagination.