You can use the Connector for VMware Tanzu Greenplum and VMware Tanzu GemFire to both mirror the entries of an entire VMware Tanzu GemFire region into a VMware Tanzu Greenplum table, and to mirror all rows in a Greenplum Database table into a GemFire region.
|Connector Version||GemFire Version||Greenplum Version|
|3.4.1, 3.4.0||9.7.x||4.3.x, 5.x|
Released: April 7, 2022
The Connector for VMware Tanzu Greenplum and VMware Tanzu GemFire 3.5.0 includes new and changed features and bug fixes.
The Connector for VMware Tanzu Greenplum and VMware Tanzu GemFire 3.5.0 includes these new and changed features:
The following issues were resolved in the Connector for VMware Tanzu Greenplum and VMware Tanzu GemFire version 3.5.0:
|31974||Fixes some reported security issues.|
Version 3.4.1 of the connector ships with VMware Tanzu GemFire version 9.8.x. The version 3.4.0 connector works with VMware Tanzu GemFire version 9.7.x. This release works with VMware Tanzu Greenplum versions 4.3.x and 5.x.
See Using the Connector for specification of the Greenplum Database schema and requirements for using the connector.
gfsh create gpdb-mapping option
--id is now optional. If the
--id option is not specified, the Connector for Tanzu Greenplum and Tanzu GemFire will look for a primary key in the Greenplum Database table. If the
--id option is not specified and there is no primary key specified in Greenplum, then the mapping will fail with the error
Table <table-name> lacks a primary key. Please use the --id option.
This also applies if the Connector for Tanzu Greenplum and Tanzu GemFire is configured in a
gfsh create jndi-binding command options have been changed in the following ways:
--jdbc-driver-classoption is now optional.
--urlis an alias for the
--typeoption defaults to
--type=POOLEDdefaults to creating a Hikari pool. Or, implement
org.apache.geode.datasource.PooledDataSourceFactoryto customize the class that implements the pool.