Tamr Documentation

Release Notes

Notes for Tamr v2020.21.0 - v2020.24.0

For information about installing a new version, see Upgrading Tamr.

Release Notes - Version v2020.023.0

These release notes list what's new in this release, corrected issues, and known issues.

New Features and Improvements

The following new feature is included in this release.

Fixed Support Issues

This release corrects the following error.

  • Spark instance type override is not picked up and used when submitting jobs. Affects versions: v2020.018.0. Fix versions: v2020.023.0.

Release Notes - Version v2020.022.0

These release notes list what's new in this release, corrected issues, and known issues.

New Features and Improvements

The following new features are included in this release.

  • Min distance between shapes as fully supported geospatial metric.
  • Relative area overlap similarity function and binning.
  • Show User Defined Signal output as columns in dedup record pairs table. See user-defined signals.

Fixed Support Issues

This release corrects the following errors.

  • gis.centroid transformation function should not double-count start/end point of a polygon boundary in calculation. Affects versions: v2020.004.1. Fix versions: v2020.022.0.
  • Convex overlap for polygons as a non-DNF comparator function. Affects versions: v2020.015.0. Fix versions: v2020.022.0.
  • Min distance between shapes as fully supported geospatial metric. Affects versions: v2020.015.0. Fix versions: v2020.022.0.

Release Notes - Version v2020.021.0

These release notes list what's new in this release, corrected issues, and known issues.

New Features and Improvements

The following new features are included in this release.

Fixed Support Issues

This release corrects the following errors.

  • Update the UI to accommodate the ability to infer pairs from cluster feedback. Affects versions: v2020.005.0. Fix versions: v2020.021.0.

Known Issues

The following are known issues.

  • When you upload a dataset into Tamr, the datatype of the primary key column must be a string-type. Tamr does not verify the datatype, resulting in errors in subsequent processes if the primary key has an integer or other datatype.
  • Status field (text and icon) on the Jobs page is not centered and the icon is truncated.
  • Mapped/Unmapped attribute filters are not working on any downstream project in a project with chained datasets, after an upgrade to v.2019.023.1 and greater. If you encounter this issue, contact Tamr Support for information about a workaround (running an internal-only API request that calculates attribute mappings in this case).
  • Column resizing on the Users page does not behave as expected.
  • The schema mapping project is not showing out-of-dateness for projects.
  • The Unified Dataset page throws an error in the user interface when you are logged in as a reviewer.
  • Job submission for chained projects may not appear immediately on the Jobs page after choosing Submit. Submit is not disabled in this case. Pre-processing of dataset versions takes place before Tamr submits the jobs to Spark and Tamr is not currently accounting for this time on the Jobs page.
  • The job for Updating results is not showing the project it is associated with on the Jobs page.
  • The upgrade process updates all record pair feedback to use unified record IDs instead of origin record IDs. This process runs automatically when upgrading. However, this process depends on Elasticsearch index being up-to-date for the unified dataset before you start an upgrade process. In cases where the index is not up-to-date at the time of upgrading to version v.2019.024 or greater, the upgrade process will have no effect and the pre-upgrade pair feedback will not be migrated or deleted. As a workaround, before you upgrade, index the unified dataset in Elasticsearch, and after you upgrade, run the following endpoint manually: /api/dedup/pairs/feedback/migrate, and then run the job that updates pairs for your project.

Known Issues with Geospatial Support

Features for working with geospatial data are currently available for beta testing only. For information about the current feature set, see Working with Geospatial Data.

Updated 6 days ago


Release Notes


Notes for Tamr v2020.21.0 - v2020.24.0

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.