You can use the Connector for VMware Greenplum and VMware GemFire to both mirror the entries of an entire VMware GemFire region into a VMware Greenplum table, and to mirror all rows in a Greenplum Database table into a GemFire region.
Supported Platforms
Connector Version | GemFire Version | Greenplum Version |
---|---|---|
3.5.0 | 9.10.x | 5.x, 6.x |
3.4.1, 3.4.0 | 9.7.x | 4.3.x, 5.x |
Release 3.5
Release 3.5.0
Released: April 7, 2022
The Connector for VMware Greenplum and VMware GemFire 3.5.0 includes new and changed features and bug fixes.
What's New and Changed in Version 3.5.0
The Connector for VMware Greenplum and VMware GemFire 3.5.0 includes these new and changed features:
- Starting with version 3.5.0, the Connector for Greenplum and GemFire is available only as a separate download for VMware Greenplum 5.x and 6.x from Broadcom Support Portal. In previous versions, the connector JAR file was included in the GemFire download package.
- The connector adds support for GemFire 9.10.x and Greenplum 6.x.
- The connector includes fixes for reported security issues.
Resolved Issues
The following issues were resolved in the Connector for VMware Greenplum and VMware GemFire version 3.5.0:
Issue # | Summary |
---|---|
CVE‑2022‑21724 | Updates the postgresql JDBC JAR file to version 42.3.3. |
CVE‑2021‑44832 CVE‑2021‑45046 CVE‑2021‑45105 |
Updates the log4j2 library to version 2.17.1. |
31974 | Fixes some reported security issues. |
Release 3.4
Release 3.4.1
What's New in Version 3.4.1
Version 3.4.1 of the connector ships with VMware GemFire version 9.8.x. The version 3.4.0 connector works with VMware GemFire version 9.7.x. This release works with VMware 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.
Resolved Issues in Version 3.4.1
- The Connector for Greenplum and GemFire currently uses an internal Apache Geode API that changed, requiring a rebuild of the Connector for Greenplum and GemFire. There are no user-visible changes or bug fixes for this patch release.
Release 3.4.0
Resolved Issues in Release 3.4.0
The
gfsh create gpdb-mapping
option--id
is now optional. If the--id
option is not specified, the Connector for Greenplum and 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 errorTable <table-name> lacks a primary key. Please use the --id option.
This also applies if the Connector for Greenplum and GemFire is configured in a cache.xml
file.
The GemFire
gfsh create jndi-binding
command options have been changed in the following ways:- The
--jdbc-driver-class
option is now optional. --url
is an alias for the--connnection-url
option.- The
--type
option defaults toSIMPLE
. - A specification of
--type=POOLED
defaults to creating a Hikari pool. Or, implementorg.apache.geode.datasource.PooledDataSourceFactory
to customize the class that implements the pool.
- The
Known Issues
- Import truncates any time or timestamp from Greenplum Database to a decimal millisecond precision. All represented microsecond precision is lost. For example, the Greenplum time of 2017-09-21 12:31:03.636847 becomes 2017-09-21 12:31:03.636 within GemFire.
Content feedback and comments