MDM: known issues and known limitations - 6.5

Talend Data Fabric Release Notes

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Open Studio for Big Data
Talend Real-Time Big Data Platform
task
Installation and Upgrade

We encourage you to consult the JIRA bug tracking tool for a full list of open issues:

https://jira.talendforge.org/issues/?filter=26953

Studio

Limitation

Description

Special characters are not allowed in a primary key.

Using special characters (for example, *, ", [ or ]) in a Primary Key may cause errors when you create, query, or delete data records.

Entities with the same name are not allowed on the same MDM server.

Entity names must be unique, both within a Data Model and across multiple Data Models deployed to the same MDM Server.

tMDMBulkload requires Java 8

Any Job using the tMDMBulkload component must be compiled and run with Java 8.

If you want to use Talend Data Stewardship to handle the merging tasks generated during the integrated matching process, pay attention to the following.

  • The integrated matching feature supports only primary keys of the type string.
  • The integrated matching feature does not support matching on entities with composite primary keys.
  • The mapping between MDM and Talend Data Stewardship only applies to simple type elements at the root level in an MDM entity, and will ignore complex type elements or repeatable elements.

There are no associated users when non-human tasks of a workflow are executed in the background.

Since there are no associated users when non-human tasks of a workflow are executed in the background, pay attention to the following two cases:
  • When performing an update of a record through a Talend connector, you can use the setUpdateUsername method to generate a correct journal event even if there is no current user available. By default, if no user name is specified, the journal event will end up with "??????" as the user name.

  • When reading or writing values of a record through the mdm_context variable, you can use the setBypassSecurity method to bypass security checks. By default, the security checks are performed on the current login user.

A foreign key element will be shown in the custom layout only if it has been rendered in the main tab

To display a foreign key element in the custom layout, you need to render it in the main tab.

The match simulation operations will not take into account the built-in blocking key

You may use the built-in blocking key when defining a match rule. However, the match simulation operations will not take into account the built-in blocking key.

You need to restart the Studio after installing required third-party libraries

After you install any required third-party libraries, you need to restart the Studio for your updates to be taken into account.

Repeating elements specified in the Viewable section of a View do not work on versions of Oracle 11g prior to 11.2

If you specify a repeating element (maxOccurs > 1) in the Viewable section of a View, it does not work on versions of Oracle 11g prior to 11.2.

tMDMDelete may take a long time to run a delete query with an Oracle database

If tMDMDelete encounters issues with a timeout when trying to run a delete query because the database takes a long time to perform this action, consult the article about how to get rid of transactions timeout for long running operations on Talend Help Center (https://help.talend.com).

tMDMConnection parameter "Use client side transaction id" is not production ready

The tMDMConnection component has a new parameter called "Use client side transaction Id". This option is experimental and is subject to change in the future, so should not be used in a production environment.

tMDMInput operator "Joins With" is reserved for future use

In the component tMDMInput, after the Use multiple conditions check box is selected, the Joins With operator listed in the Function column is reserved for future use.

Issue

Workaround

When working with the Product Demo, you should deploy the Workflows separately from the rest of the demo to avoid synchronization issues.

Specifically, do the following when you start to work with the Product Demo:

  1. Deploy all objects except the Workflow.
  2. Start the manual synchronization process from the User Management tab in the Talend MDM Web UI whenever a user or a role is created/changed to ensure that the corresponding information will be properly created in Bonita (Demo_User and Demo_Manager roles and their associated users).
  3. Deploy the Workflow.

Installer

Issue

Workaround

By default, macOS Sierra sets all downloaded files to "quarantine". This prevents you running the Studio.

  1. Unzip Talend Studio as usual.
  2. Open a Terminal window on the folder where you unzipped your Talend Studio.
  3. Execute either of the following commands: xattr -d com.apple.quarantine * or xattr -c *

Users with a recent version of Mac OS X may need to update their Gatekeeper settings to install Talend products. Gatekeeper is available from OS X 10.7.5.

  1. Click the Apple icon, and then click System Preferences.
  2. Under System Preferences, click Security & Privacy.
  3. Under Security & Privacy, click General tab.
  4. Click the lock icon next to Click the lock to make changes, and then identify yourself using the user name and password for an account with administrator rights. Only administrators can change the security settings.

  5. Under Allow apps download from, select the Anywhere radio button then confirm your choice in the dialog box that opens.

  6. Close all windows, so that your Mac automatically locks the Security & Privacy settings for you again.

  7. Install Talend Studio (or whatever other executable you want to install) by following the usual installation procedure. Note that, when you double click the Talend-Studio-macosx-cocoa.app file, you will see a warning saying that it is an application downloaded from the Internet, but if you click Open, your Mac should let you install it without further issues.

  8. Once you have completed the installation process, you can repeat the above steps to return your Security & Privacy settings to their previous value if you want.

Talend MDM Server

Issue

Workaround

Database migration may be required if your Data Model uses a reusable type more than once.

If your Data Model makes use of a reusable type more than once within one or more entities and this causes you to encounter issues, you may need to migrate your database when upgrading to this version.

For more information, see https://jira.talendforge.org/browse/TMDM-6805.

Read-committed isolation using row versioning must be activated for Microsoft SQL Server 2008

To avoid concurrency issues and deadlocks on Microsoft SQL Server 2008, MDM Server requires that you activate read-committed isolation using row versioning by running the following statement on the MDM databases:

ALTER DATABASE <database name>
  SET READ_COMMITTED_SNAPSHOT ON
  WITH ROLLBACK IMMEDIATE;

For more information, see: http://msdn.microsoft.com/en-us/library/ms188277.aspx.

When using Talend-LogServer, by default, event logs are stored without specific security protection and as such all logs are visible to anyone with access to the server (via an HTTP URL within your network).

For more information, see the article about how to deactivate the Talend Administration Center Logging Screen and Talend Log Server on Talend Help Center (https://help.talend.com).

Talend MDM Web UI

Limitation

Description

Indexing limitations on composite keys

Full text search does not support entities with composite keys.

Issue

Workaround

MDM Web User Interface supports Internet Explorer 11 in Compatibility Mode only

If you want to use MDM Web User Interface with Microsoft Internet Explorer 11, you must activate Compatibility Mode in your browser to do so. Earlier supported versions of Internet Explorer are not affected by this requirement.