2.1.1 Known Issues

The 2.1.1 release of Fusion includes the following known issues.

  • bufferDocsForSolr not enabled by default

    Enabling bufferDocsForSolr in the Solr Indexer index pipeline stage provides a better rate of ingest. However, it is not enabled by default due to a known issue in Solr. This issue will be resolved in a future release.

    If you are experiencing performance issues during ingest and no errors are found in connectors.log, api.log, or solr.log, then enabling bufferDocsForSolr may resolve the problem.

  • A Sharepoint datasource cannot be configured to index several Sharepoint sites if one or more of top-level site names are prefixes of the other names, e.g., sites "s2", "s20", and "s200" cannot be indexed by the same datasource; it is necessary to configure and use three different datasources.

  • The Azure connectors (lucid.azure.blob and lucid.azure.table) are not working.

  • The default Salesforce datasource configuration specifies the following Salesforce objects: Case, CaseComment, CaseHistory, CaseFeed, FeedComment, Asset, Account, Contact, Opportunity, Product2, Lead. The Salesforce repository must be configured to use these objects, else the datasource configuration will be invalid. If the datasource fails to save in the Fusion UI, inspect the "Objects to crawl" specification, under "Advanced" options.