Important Changes

6.10 Version

1. Notifications module org.universe.mdm.notifications

The segment for sending notifications of record insertion com.universe.mdm.notifications[SEND_UPSERT_NOTIFICATION] has changed.

After the update, the com.universe.mdm.notifications.notifications.notifications.upsert.version=1 parameter must be set to use the old version of the segment.

See the :ref:` technical change log <changelog_notif>`` for details.

6.9 Version

1. Deprecated version of REST API

In the 6.9 REST API release, v1 is marked as obsolete, so it is excluded from Universe products. The queries described below are only available in v2:

Excluded from EE:

  • org.unidata.mdm.rest.core

  • org.unidata.mdm.rest.v1.search

  • org.unidata.mdm.rest.v1.meta

  • org.unidata.mdm.rest.v1.data

  • org.unidata.mdm.rest.v1.draft

  • org.unidata.mdm.rest.v1.dq.core

  • org.unidata.mdm.rest.v1.dq.data

  • org.unidata.mdm.rest.v1.bulk.core

  • org.unidata.mdm.rest.v1.matching.core

  • org.unidata.mdm.rest.v1.matching.data

  • com.unidata.mdm.rest.v1.bulk.remove.records

  • com.unidata.mdm.rest.v1.workflow.core

Excluded from CE:

  • org.unidata.mdm.rest.core

  • org.unidata.mdm.rest.v1.data

  • org.unidata.mdm.rest.v1.meta

  • org.unidata.mdm.rest.v1.draft

  • org.unidata.mdm.rest.v1.search

  • org.unidata.mdm.rest.v1.dq.core

  • org.unidata.mdm.rest.v1.dq.data

  • org.unidata.mdm.rest.v1.matching.core

  • org.unidata.mdm.rest.v1.matching.data

  • org.unidata.mdm.rest.v1.bulk.core

2. Migration from Elasticsearch to OpenSearch

Note

In release 6.9 the migration from Elasticsearch to OpenSearch was implemented, which resulted in changes in public API

  • The org.unidata.mdm.search.service.SearchService#setIndexSettings signature has changed. The settings are passed as IndexSettings rather than Map<String, Object>. Example usage of the new class: org.unidata.mdm.job.reindex.service.impl.ReindexDataJobPrepareItemWriter#PREPARE_INDEX_PARAMS.

  • org.unidata.mdm.search.service.impl.AdminComponentImpl#getNodesInfo renamed to org.unidata.mdm.search.service.impl.AdminComponentImpl#getNodesCount and returns the number of nodes. If the rest of the node information is needed, refinement is required.

  • The constructors AdminComponentImpl, SearchComponentImpl, and SearchServiceImpl take org.unidata.mdm.search.service.impl#OpenSearchClientWrapper instead of org.elasticsearch.client.Client.

  • Changed the class returned by the protected methods of BaseComponentImpl.

  • Changed the class returned by SearchComponentImpl public methods. Such values are handled by org.unidata.mdm.search.service.impl.SearchServiceImpl#extractSearchResult(org.unidata.mdm.search.context.SearchRequestContext, java.util.List<org.universe.opensearch.client.opensearch.core.SearchResponse<com.fasterxml.jackson.databind.node.ObjectNode>>).

  • The org.unidata.mdm.core.audit.enabled.storages parameter has changed one of the possible values: es → index.

Also, when migrating to OpenSearch, additional steps are required to save audit data.

3. Authentication Checks by Username and IP Address

In the 6.9 release checks for user authentication and the task of cleaning up unused passwords were added.

When installing or updating a system, the org.unidata.mdm.core.job.clean.inactive.passwords.cronex parameter or INACTIVE_PASSWORD_CLEAN_JOB_CRONEX container environment variable must be added to the backend.properties file to start clearing passwords.

The rest of the parameters are available for editing through the UI and require no additional writing to the file.

4. Updating User Rights Without Logging Out

Updating user rights, roles and groups is done without logging out of the system and reauthorizing:

  • If the user updates his own settings, the changes will automatically update on the UI.

  • If the user updates another user's settings, a modal window will appear on the screen of the user who has an active session to accept the updates.

5. Additional Audit Events

When updating the system from an existing database, new audit events will be available only after performing the following actions:

  • In the system parameter "Audit Log Storage" (org.unidata.mdm.core.audio.enabled.stores), add the value "index".

  • Update the audit paths "Core Module Message Routes" (org.unidata.mdm.system.messaging.domains.core-messaging) from core.xml.

6. Updating Excel Template for Records Import/Export

The name of the list of complex attribute in the XLSX file was changed. Now the name of the attribute itself and the name of the nested object are specified.

To import files created in version 6.8 and older, you must change the name of the sheet of nested objects. Otherwise such sheet will be skipped during import, complex attributes will be empty for new records or will remain unchanged when editing existing records.