Data Access Gateway 4.0 Release Notes
These notes describe the 4.0 release of the Data Access Gateway.
These release notes contain only data-fabric-specific information and are not necessarily cumulative in nature. For information about how to use the release notes, see Ecosystem Component Release Notes.
| Version | 4.0 |
| Release Date | January 2022 |
| MapR Version Interoperability | Compatible with release 6.2 with EEP 7.0.0 and later* |
| Package Name | mapr-data-access-gatewayTo view the full list of package names, navigate to https://package.ezmeral.hpe.com/releases/MEP/ and select your EEP and OS. |
| Documentation | Administering the Data Access Gateway |
*The latest core 6.2.0 EBF patch must be applied before you can use Data Access Gateway 4.0 on release 6.2.0.
New in This Release
Only Data Access Gateway 4.0 can be used with release 7.0.0 in FIPS mode. This is the only significant difference between Data Access Gateway 3.0 and 4.0. Both versions 3.0 and 4.0 can be used in non-FIPS mode.
| Client | Supported EEPs |
|---|---|
| MapR Database JSON REST API | EEP 5.0.0 and later |
| Python OJAI client | EEP 6.0.0 and later |
| Node.js OJAI client | EEP 6.0.0 and later |
| C# OJAI client | EEP 6.0.0 and later |
| Go OJAI client | EEP 6.0.0 and later |
| Java OJAI Thin Client | EEP 6.3.0 and later |
Configuring the Maximum Message Size for the gRPC Service
EEP 7.1.0 and later support a new configuration
option (grpc.service.max-message-size) that allows you to change the
maximum message size that the gRPC service accepts. For details, see Administering the Data Access Gateway.
In EEP 7.1.0 and later, the Java OJAI Thin Client
supports an OJAI Connection String option (maxmsgsize) to change the
maximum message size that the gRPC client accepts. For details, see Using the Java OJAI Thin Client.
Fixes
None.
Known Issues and Limitations
None.
Resolved Issues
None.