User GuidesAPI ReferenceRelease NotesEnrichment APIs
Doc HomeSupportLog In

Tamr Core Release Notes

These release notes describe new features, improvements, and corrected issues in each Tamr Core release.

See our Security page for the latest security updates and resources.

Tamr Core Releases

Important Information for All Releases

Upgrading Tamr Core to a New Release

Follow the upgrade instructions in the Tamr Core documentation for the version to which you are upgrading. If the version to which you are upgrading has patch releases, Tamr strongly recommends installing the latest patch to ensure you have the latest fixes and security enhancements.

Depending on the version from which you are upgrading, you may need to install required checkpoint releases as part of your upgrade path.

Required Checkpoint Releases

When you upgrade Tamr Core, you must upgrade to each of the intervening checkpoint versions before upgrading to a later version.

The following Tamr Core releases are checkpoint releases:

  • v2022.002
  • v2022.001
  • v2021.002
  • v2020.016
  • v2020.004

The upgrade utility prevents you from upgrading past a checkpoint version. For example, the following upgrade paths are allowed: v2020.017 -> v2021.002, v2021.001 -> v2021.002. These upgrade paths are prevented: v2020.016 -> v2021.003, v2019.019 -> v2021.002.

Installing Patch Releases

For every software release version that has a patch, Tamr strongly recommends that you upgrade to the most recent patch. To install the most recent patch, follow the upgrade instructions and supply the version number of the patch as the version for your upgrade.

If you want to upgrade directly to a patched version, specify the --skipCheckpointReleaseValidation flag when installing Tamr Core. For information, see Upgrading.

Known Issues

To view current known issues, please consult the Tamr knowledge base.


Tamr Core 2022 Releases

v2022.004.0 Release Notes

Important Support Notes for this Release

This release is not supported for AWS cloud-native deployments.

New Features and Improvements

The following new features are included in this release.

  • Increase default value of TAMR_HTTP_IDLE_TIMEOUT to 300s.
  • EnrichmentComponent does not handle attribute value where first array element is null. This changes the handling of attributes which are arrays (of strings). Previously, if the first element of the array was null, the enrichment failed. Now it uses the first non null element as the value to be enriched. If all elements are null, the array is empty, or the attribute is null, the default value "" is used.

Back to top


v2022.003.0 Release Notes

Important Support Notes for this Release

This release is not supported for AWS cloud-native deployments.

New Features and Improvements

The following new features are included in this release.

  • Optimize cluster editing operations in mastering projects. This change increases performance when processing edit requests. Note that when upgrading to this release, you must run an “Update results” job from the Pairs page before you can edit clusters.
  • For DMS, remove ability to select greater than "8" thread count in the UI and API. Tamr supports up to 8 threads for data import when using the Data Movement Service (DMS); the UI and API have been updated to reflect this maximum supported thread count.
  • Remove the Google BigQuery option in the Connect to Source page. Tamr Core has deprecated support for BigQuery, and as of this release the BigQuery option is no longer available in the Connect to Sources page when uploading datasets.
  • Browser support for Chrome and Edge in Windows 7, 8, and 10 for versions going forward. Deprecated browser support for IE11 in all versions of Tamr Core. See Requirements for Installing Tamr Core.

Fixed Issues

This release corrects the following errors.

  • Preview button not working. Found in: v2021.020.0. Fix versions: v2022.003.0. When writing any type of transformation for both input and unified datasets, the “Preview” button in the transformations cell doesn't work.
  • Bootstrapping Do Not Map attributes should not create empty unified attributes. Fix versions: v2022.003.0. Do Not Map attributes are now ignored when bootstrapping multiple source attributes.
  • Token weighting should be hidden in categorization projects. Fix versions: v2022.003.0. Because token weighting is not utilized for categorization projects, the option to select token weighting for machine learning attributes has been removed in Schema Mapping for these projects.

Back to top


v2022.002.0 Release Notes

New Features

The following new features are included in this release.

New Checkpoint Releases

Tamr Core releases v2022.001.0 and v2022.002.0 are checkpoint releases. When you upgrade Tamr Core, you must first upgrade to v2022.001.0, and then v2022.002.0, before upgrading to a greater version.

Upgrade to HBase 2.x Client

This release includes an upgrade of the HBase Java libraries used by Tamr Core from 1.3.1 to 2.2.3. Additionally, the version of HBase that is installed on single-node instances has been upgraded from 1.3.1 to 2.3.6. See Upgrading Tamr Core. If you are upgrading a cloud-native deployment, please contact Tamr Support for guidance.

❗️

Important

  • For single-node deployments, you must provide an additional flag, --exportHBaseSnapshots, to the admin utility (unify-admin.sh) during upgrade. To prevent data corruption, see prerequisites before upgrade.
  • Upgrading HBase versions requires significant upgrade time; expect upgrade to take longer than usual for this release. Upgrade time is highly dependent on the number of projects in your pipeline. For example, if you have 20 projects, expect that upgrade to take at least 3 hours.

Improvements

  • Schema mapping projects: user interface improvement for mapping suggestion counts. The number next to lightbulbs now indicates the top suggested mappings for an attribute at the specified similarity threshold.

Fixed Issues

This release corrects the following errors.

  • Schema mapping suggestion counts are zero or negative for some attributes. Found in: v2021.015.0. Fix versions: v2022.002.0.

Known Issues

Note: For this release, IAM role-based authentication for S3 on DMS storage is not supported on EC2 instances. Tamr recommends using a service principal to import or export data from AWS.

Back to top


v2022.001.1 Patch Release Notes

This patch release corrects the following issues.

  • Running into malformed YAML issue when upgrading from v2021.006 to v2022.001.

v2022.001.0 Release Notes

New Features and Improvements

The following new features are included in this release.

  • Upgrade the bundled JDK version.
  • Show correct empty state when using the filters in Dataset Catalog page. When using the "Results and Internals" or "System" filter in Dataset Catalog, the message shown in the empty state is now “No datasets matching your filters.”
  • Add disk space available check to upgrade utility. Validation scripts now include a utility to verify that at least 20% of disk space is available when starting or upgrading Tamr Core.

Fixed Issues

This release corrects the following errors.

  • Clustering job stuck. Found in: v2021.010.2. Fix versions: v2022.001.0.
  • Validation script does not correctly identify disk usage scenarios that will break Tamr Core. Found in: v2021.019.0. Fix versions: v2022.001.0.

Back to top