Release Notes 3.0

What’s New

Apache Solr as an external service

As of this version, the internal search component Apache Solr is no longer delivered as part of smart.finder. To ensure the functionality of smart.finder, Apache Solr must be provided as an external service in your infrastructure.

Information on installing Apache Solr can be found at Required software.

Information on the configuration of smart.finder in your Apache Solr instance can be found at Apache Solr configuration.

map.apps Smart Search Extension discontinued

As of this version, map.apps Smart Search will no longer be maintained as an independent extension. The Smart Search functionality is fully integrated into smart.finder and can be used as usual.

A detailed overview of the changes and the steps for updating to this version can be found in the update notes at map.apps Smart Search Extension.

Standalone client discontinued

The client application of smart.finder is no longer provided as part of the product from this version onwards. An existing map.apps instance is required to use the delivered apps and bundles of smart.finder.

The installation of the smart.finder bundles and apps is described in the section Installation of the client web app.

For the operation of the server component, map.apps is not required.

Result Center support ends with map.apps version 4.20

The Result Center (bundle resultcenter) will no longer be shipped with map.apps as of map.apps version 4.20. We recommend using the new result-ui bundle in combination with the sf_result-ui bundle instead.

If you want to keep using the resultcenter bundle, you can still download the latest version from the con terra Developer Network. The bundle sf_resultlist-resultcenter, which is required to integrate the Result Center into smart.finder, is still part of smart.finder.

Filter for indexing external CSWs

When indexing external OGC Catalog Services or INSPIRE Discovery Services, an optional filter can now be specified. This means that, for example, only documents with a specific keyword or within a defined spatial area can be indexed. If no filter is specified, the entire content of the service is indexed.

Integration Job Manager

The standalone client setting eliminates the need to call up the Job Manager from the supplied apps. This is integrated in a separate tab in the map.apps Manager and can be used here as usual.

The sidebar and tool for calling up the Job Manager have therefore been removed from the apps.

Update Notes

If you skip several versions during the update, please also follow all update notes of the intervening versions.

No longer supported properties

solr.solr.home

Directory path to solr.home.

New properties

solr.server.url

URL to the Apache Solr instance used.

Default value: http://localhost:8983/solr

Renaming of Java packages

The basic Java packages have been renamed from de.conterra.finder to de.conterra.smartfinder.

This change also affects the configuration files of the respective indexes (conf/solrconfig.xml and conf/schema.xml ), as the Java classes are referenced here (e.g. RequestProcessorFactory, FieldType, etc.).

The map.apps Smart Search Extension is now part of smart.finder. In the course of the integration, small optimizations were made to the configuration and naming, which are documented below.

Renaming of the Solr index

The Solr index has been renamed from smartsearch to featuresearch.

Integration of map.apps Bundle

The functionality of the map.apps bundle sf_smartsearch has been integrated into the bundle sf_store.

The following adjustments were made.

Component SmartSearchStore

The SmartSearchStore component has been renamed FeatureDocumentStore and is now part of the sf_store bundle.

The following properties could be configured on the SmartSearchStore component up to smart.finder version 3.x. As of smart.finder version 3.x, these properties are no longer supported. The configuration is now carried out using Search templates (QueryTemplates).

  • editDistance

    The fuzzy search is now defined within a search template. This is configured in the FeatureDocumentStore component using the queryTemplate property.

    See also: Fuzzy Search or in the Documentation of the sf_store bundle.

  • singleBoostWeight, groupedBoostWildcardWeight, groupedBoostWeight

    These properties were used to influence the weighting of search results. The weighting is now used within a search template (QueryTemplate). The FeatureDocumentStore component contains a predefined search template, which contains the original default values. This search template can be customized using the queryTemplate property.

    See also: search templates or in the documentation of the sf_store bundle.

Please note that when migrating from map.apps Smart Search Extension 2.x to smart.finder 3.x, the server component must be migrated, as Apache Solr is no longer delivered as part of smart.finder. The setup of Apache Solr is described in the following section.

Client application

A map.apps instance is required to use the smart.finder bundles and apps.

The installation of the smart.finder bundles and apps is described here.

Apache Solr configuration

The provision of an Apache Solr instance is required to operate smart.finder. Information on the installation and configuration of Apache Solr can be found at https://solr.apache.org/.

Use the full variant as Apache Solr distribution. The ‘slim’ variant does not contain the required modules and is therefore not suitable.

As Apache Solr is now operated as an external service, this results in the following changes for smart.finder:

solr.home configuration

The indexes are managed and persisted in the SOLR_HOME directory. The SOLR_HOME directory is located under [SOLR_INSTALL_DIR]/server/solr by default.

You can also start Apache Solr with a different directory. In this case, you must adapt this accordingly. The following options are available here:

  • in the file [SOLR_INSTALL_DIR]/bin/solr.in.sh (Linux) or [SOLR_INSTALL_DIR]/bin/solr.in.cmd (Windows)

  • as a system environment variable

  • when starting Apache Solr with the parameter --solr-home <dir>

Copy the contents of the directory [RELEASE-ORDNER]/solr/cores into the SOLR_HOME directory. You will then see the following directory structure:

/SOLR_HOME
 /core0
 /featuresearch
 /indexingmanagement
 /lib
 /...

Now copy the file SOLR_HOME/lib/jts-core-[VERSION].jar into the directory [SOLR_INSTALL_DIR]/server/solr-webapp/webapp/WEB-INF/lib. The presence of this library in exactly this location is predefined by Apache Solr.

Migration of existing indexes

To migrate existing indexes, it must be ensured that the conf/solrconfig.xml file of the respective cores matches the files supplied in version 3.

If you have made changes to the conf/solrconfig.xml and conf/schema.xml files or use completely customised cores, it is recommended that you compare these files with the version 3 files supplied and make any necessary changes.

After changing the conf/schema.xml file, the respective indexes must be rebuilt.

Discontinued Features

  • The standalone client of smart.finder has been removed.

  • The omnisearch bundle is no longer used. The app sf-full-screen-map-omnisearch has been removed.

Deprecated Features

  • The security.mode ONLY_AUTHN will be discontinued in one of the future versions.

Known Limitations

SNR-1129

[Security] Support secured Solr server instance

Changelog

3.0.0

New Features and Improvements

SNR-936

[Server] Decoupling smart.finder service from Apache Solr

SNR-1100

[Bundles] Integrate Smart Search bundles with smart.finder

SNR-1075

[Indexing] Support filter constraints with CSW jobs

SNR-1120

[Documentation] Add clause on NODE_TLS_REJECT_UNAUTHORIZED in CLI usage

SNR-1127

[Rollout] Remove Standalone Client

Fixed Issues

SNR-1107

[Bundles] sf-dialog-container element is missing in RootComponent.vue

SNR-1116

[Documentation] Wrong URL for login with CLI

SNR-1117

[CLI] Unable to export jobs with special characters in title