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.
Obtaining Release Binary Files
Contact Tamr Support for release binary files for installation and upgrade. Checksums are available for binary validation.
Additional Resources
The Help Center is a self-guided knowledge base with troubleshooting tips and procedures.
Tamr Core 2023 Releases
v2023.02.1 Patch Release Notes
This patch extends the --skipEnvironmentValidation upgrade flag to exclude all validators.
Note: Use this flag with caution. It allows the upgrade process to proceed even with an invalid system configuration, which will cause the process to fail.
v2023.002.0 Release Notes
New Features and Improvements
This release includes the following new features.
- Add ability to disable live preview on Group Records page
You can now control whether the live preview of the results of record grouping appears: an Enable Preview toggle is now included on the Group Records page. Turning preview off can speed up editing of the record grouping definitions when many edits need to be made at once. It is recommended, but not required, that you re-enable preview before saving and running record grouping to allow you to review your changes before committing them. - New Core Connect API parameter to keep data types
This release adds an option, simplifiedDataTypesEnable, for Core Connect JSON exports to S3 and serverfs. When you set simplifiedDataTypesEnable to false, data is exported using the data types registering for the dataset you are exporting within Tamr Core. By default, simplifiedDataTypesEnable is true, which maintains the previous behavior of JSON exports: data types are simplified and all columns are exported as arrays of strings, unless flattenEnable is also true, in which case all columns are exported as strings.
- When simplifiedDataTypesEnable=true && flattenEnable=false, all data is exported as array of string type.
- When simplifiedDataTypesEnable=true && flattenEnable=true, all data is exported as string type.
- When simplifiedDataTypesEnable=false, data is exported matching the type for its column as defined in the dataset service (regardless of the setting of flattenEnable).
Fixed Issues
This release corrects the following errors.
- Non-functional Max Learned Pair UI checkbox. Found in: v2022.011.0, v2022.012.0. Fix versions: v2023.002.0. This release addresses two issues with the Max Learned Pair setting in the Edit Project dialog. Previously, the value for this setting was reset to 0 if the browser was refreshed. In addition, editing the value in one project updated the value within the UI for all projects. Both errors have been fixed.
- NullPointerException on EmrFileSystem.exists. Found in: v2023.001.0. Fix versions: v2023.002.0. This release fixes an issue on AWS scale-out deployments. Spark jobs no longer fail when a file doesn't exist on S3.
- New keys for ingest endpoints are also included for export endpoints. Found in: . Fix versions: v2023.002.0. Previously, Core Connect import-related JSON keys (policyIds, primaryKey, profile, recipeId, truncateTamrDataset) were also being shown in the Swagger examples for export endpoints. These superfluous keys have been removed from the export Swagger examples.
- S3 client can't upload large files (+5GB). Found in: v2022.009.0. Fix versions: v2023.002.0. This release corrects an error that prevented the Tamr Core S3 client from uploading files larger than 5GB to S3.
v2023.001.0 Release Notes
New Features and Improvements
This release includes the following new feature:
- Upgrade the Hadoop/Spark libraries for single-node deployments
Upgraded the version of Spark used by Tamr Core to Spark 3.1 3. Starting with this release, Tamr Core uses Spark 3.1.3 instead of Spark 2.4.5, which it used in previous releases. The upgrade to Spark 3.1.3 takes place automatically as you upgrade to this release.
For more information, see Upgrading Tamr Core.
Fixed Issues
This release corrects the following error:
- Pair not appearing after Non-ES Backup Restoration in project with record grouping. Found in: v2022.006.0, v2022.011.0. Fix versions: v2023.001.0. The Reindex API now reindexes record groups when Record Grouping is enabled.