2.4.0 Known Issues
The 2.4.0 release of Fusion includes the following known issues:
Time-based partitioning does not work with the
edismax) ignores Boolean OR when
mmis not explicitly set
This behavior is new to Solr 5.5.0 and is fixed in 5.5.2 and above. A future release of Fusion will include that fix.
bufferDocsForSolrnot enabled by default
bufferDocsForSolrin 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
solr.log, then enabling
bufferDocsForSolrmay resolve the problem.
Stopped Aggregator jobs may continue running in Spark
After stopping an aggregator job using the Fusion UI or the Aggregator API, it may continue running in Spark. To work around this, go to
http://localhost:8767/on the Fusion host and click kill next to the running job.
System threads page in the UI does not send ID with request
system/threadsAPI endpoint works as expected, the Web-based interface at Applications > System > Threads fails to send the
idfield, and an API error is displayed in the Notifications panel. The workaround is to use the API directly.
Windows Server 2008 RC2 - Fusion fails to start with exceptions
Error message: "Missing jansi libraries" Installing the MS VC++ 2008 package fixes it, downloads and information are available from: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15336.
Some Gazetteer pipeline stages are not compatible with 2.3
If your existing Fusion installation utilizes the
entityDefinitionsfield in Gazetteer Lookup Extraction pipeline stages, those pipelines may break after upgrading to this release. The
entityDefinitionsfield has been renamed to