Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When you change the outputUnits value (e.g. from 10000 to 1000), you need to clean up the JCR rankings workspace. Otherwise, an error will appear when you select a search result. This is because the networks loaded into memory were created using a configuration that no longer exists, rendering any stored results obsolete. When you change the outputUnits value, make sure that you delete any stored networks and log into the Magnolia instance again to regenerate networks using the new configuration (see Clearing Result Ranker memory).

Changing configuration

The Periscope Result Ranker module configuration resides in periscope-result-ranker/src/main/resources/periscope-result-ranker/config.yaml. The module is deployed as a JAR file, but you can change the configuration by one of the following means:

...

The Java bean representation of the selected resource is then stored in the registry. The object in the registry may get decorated if a decorator exists for that configuration.

Tip

Storing configuration in the JCR resources workspace is useful for hotfixes and patches. This way, an administrator can create an urgent fix and publish it in the Resource Files app. In the long run, we recommend using file-based decoration.