Tamr Documentation

Release Notes

Notes for Tamr v2020.17.0 - v2020.20.0

Release Notes for v2020.18.0
Release Notes for v2020.17.0

Release Notes for v2020.18.0

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

What's New

In this release these changes were made:

  • Deployment on Microsoft Azure. See Deploying Tamr on Azure.
  • Test clusters produce cluster precision and recall. See Filtering Clusters.
  • A predefined list of datetime formats is now supplied for the datetime_to_iso and date_and_time_to_iso functions. These formats are applied after any formats specified in your transformations. See Working with Dates.

Fixed Support Issues

The following support issues were fixed in this release.

  • Golden Records: Error using top: The 1st argument to function top must be a constant literal expression. Affects versions: v2020.011.0. Fix versions: v2020.018.0.
  • Bulk unmap button in Schema Mapping does not work. Affects versions: v2020.012.0, v2020.014.0, v2020.016.0. Fix versions: v2020.017.0, v2020.018.0, v2020.016.1.
  • Golden Record Page keeps freezing. Affects versions: v2020.017.0. Fix versions: v2020.018.0.
  • UI doesn't show average confidence . Affects versions: v2019.023.1, v2020.016.1, v2020.016.2. Fix versions: v2020.018.0, v2020.016.3.
  • "Open details" button is not clickable on taxonomy page. Affects versions: v2020.015.0. Fix versions: v2020.018.0.
  • Train predict failure. Affects versions: v2020.016.0. Fix versions: v2020.018.0, v2020.016.2.
  • Jobs failing possibly due to incorrect path setting with spark 2.4. Affects versions: v2020.016.0. Fix versions: v2020.018.0, v2020.016.2.
  • Some links that open the Tamr UI in a new tab cause the original tab to become unresponsive on closing the new tab.
  • Mapped/unmapped filters on unified attributes is broken.
  • Average confidences for categorizations not showing for systems upgraded from v37.1.

Known Issues

The following known issues exist in this release.

  • 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 in beta. For information about the current feature set, see Working with Geospatial Data.

Upgrade

For information, see Upgrading Tamr.

Release Notes for v2020.17.0

These release notes list what's new in this release, improvements, and bug fixes.

What's New

In this release these changes were made:

  • You can view the cluster from the golden records page.
  • The process of restoring from backup is improved and retains the PostgreSQL configuration from the pre-upgrade release.

Fixed Support Issues

The following support issues were fixed in this release.

  • Fixed an issue where unmapping an attribute in the schema mapping project does not work. Affects versions: v2020.012.0, v2020.014.0, v2020.016.0. Fix versions: v2020.017.0, v2020.018.0, v2020.016.1.
  • Provided ability to view the clusters from the golden records page. Affects versions: v2019.021.0. Fix versions: v2020.017.0.
  • Fixed an issue where Generate pairs and Open exclusions were not displayed correctly in the user interface. Affects versions: v2020.015.0. Fix versions: v2020.017.0.
  • Fixed an issue where Accept cluster suggestion resulted in the "Cannot read property 'name' of undefined" error.
  • Fixed an issue wher the Elasticsearch configuration parameter TAMR_ES_MAX_RESULT_WINDOW was not applied to new projects and required manual workarounds. Affects versions: v2019.009.0. Fix versions: v2020.017.0.
  • Fixed an HTTP 500 error issued by Elasticsearch if no clusters were generated. Affects versions: v2020.016.0. Fix versions: v2020.017.0, v2020.016.1.
  • Fixed an issue where an upgrade to Tamr v2020.16 resulted in errors looking for non-existent clusters. Affects versions: v2020.016.0. Fix versions: v2020.017.0, v2020.016.1.
  • Fixed an issue where the bulk match service didn't work on an AWS scaled out deployment. Affects versions: v2020.007.1. Fix versions: v2020.017.0.

Known Issues

The following known issues exist in this release.

  • 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 in beta. For information about the current feature set, see Working with Geospatial Data.

Upgrade

For information, see Upgrading Tamr.

Updated 4 days ago


Release Notes


Notes for Tamr v2020.17.0 - v2020.20.0

Suggested Edits are limited on API Reference Pages

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