Version End of Life. Not Yet Set
Release 7.1.0 is the next major v7 release containing a number of important bug fixes and key new features.
The following changes have been made to Tungsten Replicator and may affect existing scripts and integration tools. Any scripts or environment which make use of these tools should check and update for the new configuration:
Improvements, new features and functionality
Running tpm uninstall will now save all of the Tungsten database tracking schemas for later use. There is also a new tpm keep command, which allows the tracking schemas to be saved to disk at any time in multiple formats (.json, .dmp and .cmd)
Issues: CT-2131
Added tpm flag deploy-systemd
as a more meaningful alias to install
Issues: CT-2152
Added a new option --preserve-schema
to the tpm uninstall
command in order to leave the tracking schema in the database.
Issues: CT-561
A new command tpm cert has been added to aid in the creation, rotation and management of certificates for all areas of Tungsten.
Known limitations: Percona 5.6, and all versions of MariaDB do not provide the mysql_ssl_rsa_setup command required by tpm cert gen mysqlcerts.
Issues: CT-2085
The tpm diag command now supports the --skipsudo
and --nosudo
arguments to prevent operations from using the sudo command. Using this option may result in tpm diag
skipping/failing various gathers due to a lack of access.
Issues: CT-2146
A new applier is now available that replicates to csv files on S3 storage.
For more information, see S3 Applier Docuemntation
Issues: CT-606
A new shardbyrules
filter has been added that will allow rule based sharding of replication based on user
confgurable rules that would allow sharding at table level, whereas previoulsy sharding would only be handled at schema level.
For more information, see shardbyrules Filter Docuemntation
Issues: CT-2164
Improved a query that is run by Tungsten when fetching tables metadata (column names, datatypes, etc). While it is not generally needed, the unoptimized query can run badly (especially) against old mysql versions with a lot of databases / tables. For now, the new optimized query is not used by default, but this could change in some future version.
This can be enabled by using the following property :
property=replicator.datasource.global.connectionSpec.usingOptimizedMetadataQuery=true
Issues: CT-2077
Fixed an issue while processing geometry data with SRID 4326 that would swap longitude and latitude. This applies only to MySQL 8, as prior MySQL versions do not allow specifying the order when applying a WKB (Well-known binary) to MySQL
Issues: CT-2172