Funnelback 14.2.1 release notes
Released: 23rd March 2015
14.2.1 - Selected improvements and bug fixes
-
Fixed a problem in the collection update script when processing faceted_navigation.cfg.
-
Fixed a problem which caused some collections on Windows to remain in an updating state after the completion of an update.
-
Restored Jetty webserver rewrite rule support.
Patches
Type | Release version | Description |
---|---|---|
3 Bug fixes |
Fixed an issue where the user editing interface for a user with no permitted collections would be presented with all collections selected, rather than none. |
|
3 Bug fixes |
Upgrades the Jetty web server to the latest 9.2.x version to fix a buffer bleed vulnerability. |
|
3 Bug fixes |
Fixes a bug with Push where it would create errant Vaccuum tasks while the push collection was shutting down. |
|
3 Bug fixes |
Fixes a bug where the Index Merger sometimes fails. |
|
3 Bug fixes |
Improves the logging of the indexer specifically for logging when external metadata is used as well as for storing metadata in the index. |
|
3 Bug fixes |
Improves the indexer so that metadata that is associated with internally defined metadata classes are not stored in the index unless the metadata class is defined in |
|
3 Bug fixes |
Improved the indexer so that values in XML elements that are not defined in |
|
3 Bug fixes |
Fixes a issue with the indexer reading |
|
3 Bug fixes |
Fixes a issue with Push collections, where filtering was unable to use Tika to filter documents. |
|
3 Bug fixes |
Improves Push so that the reason commits are disabled is remembered. |
|
3 Bug fixes |
Improves Push so that the log folder for the last failed commit and merge is not deleted through log rotation. |
|
3 Bug fixes |
Adds a feature to Push so that if |
|
3 Bug fixes |
Fixes an issue with click logs processing during indexing, where a invalid click log line can cause indexing to fail. |
|
3 Bug fixes |
Allows update-configs to update a single collection, rather than the entire server. To use this new capability provide update.configs.pl with the directory for the collection (e.g. /opt/funnelback/conf/collection_name/) and the upgrade process will be run only on that directory. Note that running this will not create an empty updates statistic database in admin/reports/collection_name which might be required when upgrading from some old versions. |