Using The Connector
The connector is included with Pivotal GemFire. The connector’s JAR file will automatically be included on the classpath.
To use the connector,
specify the correct
xsi:schemaLocation attribute in the
For the 3.2.0 connector, use
Connector Requirements and Caveats
Export is supported from partitioned GemFire regions only. Data cannot be exported from replicated regions. Data can be imported to replicated regions.
The number of Pivotal Greenplum® Database (GPDB) segments must be greater than or equal to the number of Pivotal GemFire servers. If there is a high ratio of GPDB segments to GemFire servers, the GPDB configuration parameter
gp_external_max_segsmay be used to limit GPDB concurrency. See gp_external_max_segs for details on this parameter. An approach to finding the best setting begins with identifying a representative import operation.
- Measure the performance of the representative import operation with the default setting.
- Measure again with
gp_external_max_segsset to half the total number of GPDB segments. If there is no gain in performance, then the parameter does not need to be adjusted.
- Iterate with values of
gp_external_max_segsthat are half as much at each iteration, until there is no performance improvement or the value of
gp_external_max_segsis the same as the number of GemFire servers.
Upgrading Java Applications from Version 2.4 to Version 3.x
API changes implemented for version 3.0.0 that are also in this connector version require code revisions in all applications that use import or export functionality.
For this sample version 2.4 export operation, an upsert type of operation was implied:
// Version 2.4 API long numberExported = GpdbService.createOperation(region).exportRegion();
Here is the equivalent version 3.x code to implement the upsert type of operation:
// Version 3.x API ExportConfiguration exportConfig = ExportConfiguration.builder(region) .setType(ExportType.UPSERT) .build(); ExportResult result = GpdbService.exportRegion(exportConfig); int numberExported = result.getExportedCount();
For this sample version 2.4 import operation,
// Version 2.4 API long numberImported = GpdbService.createOperation(region).importRegion();
here is the version 3.x code to implement the import operation:
// Version 3.x API ImportConfiguration importConfig = ImportConfiguration.builder(region) .build(); ImportResult result = GpdbService.importRegion(importConfig); int numberImported = result.getImportedCount();
Please note that the new
result objects’ counts are of type
instead of type
This is for consistency,
as the connector internally uses JDBC’s