GridDB Release Notes

Revision: 4.3.2-9

1 Introduction

This document describes about release notes of GridDB Standard Edition, Advanced Edition (These products are represented simply as GridDB in this document). The description includes information, such as product requirements and manuals, required to use GridDB. Please read this document before using GridDB.

The contents of this document are as follows.

  1. Introduction
  2. Overview and Changes
  3. Function list
  4. Product requirements
  5. Installation packages
  6. GridDB manuals
  7. Dealing with problems
  8. Important notes and limitations
  9. Notices
  10. Trademarks
  11. Supplementary explanation


2 Overview and Changes

2.1 Overview of GridDB

GridDB is a key-value datastore which can handle, store and search, an enormous amount of data at high speed and safely. GridDB has the following features.


The product family of GridDB is as follows.

GridDB Standard Edition (SE) NoSQL database product
GridDB Advanced Edition (AE) NewSQL database product with SQL interfaces

These products are individual products. But GridDB AE includes GridDB SE functionally, in other words, GridDB AE is a product which has the features and functions of GridDB SE with additional SQL functions. Note that supported functions are different depending on the purchased product.


For checking functions provided by GridDB, see "GridDB Features Reference" (GridDB_FeaturesReference.html).

For starting to use GridDB, see "GridDB Quick Start Guide" (GridDB_QuickStartGuide.html).

See Fixlist.pdf in the installation media for the correction records including bug fixes.

2.2 Changes in V4.3.2

GridDB Standard Edition V4.3.2 and Advanced Edition V4.3.2 are released. The abstract of the function enhancements is as below.

<Functions for development>

2.3 Changes in V4.3.1

GridDB Standard Edition V4.3.1 and Advanced Edition V4.3.1 are released. The abstract of the function enhancements is as below.

<Functions for development>

<Supplementary explanation>

2.4 Changes in V4.3

GridDB Standard Edition V4.3 and Advanced Edition V4.3 are released. The abstract of the function enhancements is as below.



<Functions for development>

<Operation functions>

The following points are changed from GridDB V4.2.

2.5 Changes in V4.2.5

GridDB Standard Edition V4.2.5 and Advanced Edition V4.2.5 are released.

2.6 Changes in V4.2

GridDB Standard Edition V4.2 and Advanced Edition V4.2 are released. The abstract of the function enhancements is as below.


<Functions for failure analysis and performance analysis>

<Functions for development>

<Programming language>

<Supplementary explanation>

The following points are changed from GridDB V4.2.

2.7 Changes in V4.1

GridDB Standard Edition V4.1 and Advanced Edition V4.1 are released. The abstract of the function enhancements is as below.

<Data Management functions>

<Operation functions>

<Programming language>

<Supplementary explanation>


The following points are changed in GridDB V4.1.


2.8 Changes in V4.0.3

GridDB Standard Edition V4.0.3 and Advanced Edition V4.0.3 are released.


2.9 Changes in V4.0.2

GridDB Standard Edition V4.0.2 and Advanced Edition V4.0.2 are released.


2.10 Changes in V4.0

GridDB Standard Edition V4.0 and Advanced Edition V4.0 are released.   Following features are changed in GridDB V4.0.

3 Function list

The functions of GridDB SE and AE are as follows.

Title Features Standard Edition Advanced Edition
Cluster Cluster configuration
Distributed data management
Data Management Collection
Timeseries container
Table Partitioning
Query Language TQL
API NoSQL Interface (Java/C)
NewSQL Interface (JDBC/ODBC)
Operation Control Backup
Integrated operation control GUI
Operating commands
Time series data Expiry release
Long term archive


4 Product requirements

The product requirements of GridDB are as follows. The requirements are different for the server and the client.

4.1 Server: Platform to run the database server

CPU x64 processor, 2.0GHz (minimum) or higher
Memory 1.0GB (minimum) or more
Disk Space This is the requirement only for installation. Separate space is required for database and log files. The size depends on the application (at least 1.0GB).
OS Red Hat Enterprise Linux 6.7/6.8/6.9/6.10 (64bit)
Red Hat Enterprise Linux 7.4/7.5/7.6/7.7 (64bit)
CentOS 6.7/6.8/6.9/6.10 (64bit)
CentOS 7.4/7.5/7.6/7.7 (64bit)

Following specifications or higher performance hardware is recommended for the server.

CPU x64 processor
Operating frequency 2.66GHz
Number of CPUs 2
Number of Cores 4
Memory 32GB


4.2 Client: Platform to run the developed application

Required specifications for the application using Java API, C API, JDBC, Python, Node.js or Go


Required specifications for the application using ODBC or Windows C API


Required specifications for operation control commands


Required specifications for database (Oracle) used by the import tool (RDB linkage)


4.3 Platform to use the integrated operation control GUI (gs_admin)


4.4 Platform to use the Web API

4.5 Operation platform for the Dockerfile sample

4.6 User Guide for GridDB Template for Ansible Operation Platform


5 Installation packages

There are 9 RPM packages.

Package File name Description
Server package griddb-XX-server-X.Y.Z-linux.x86_64.rpm This package contains GridDB server module and operation commands for server start-up, backup/restore database, etc.
Client package griddb-XX-client-X.Y.Z-linux.x86_64.rpm This package contains operation control commands except for server start-up, backup/restore of database, export/import, integrated operation control GUI (gs_admin) and cluster operation control command interpreter (gs_sh).
Web API package griddb-XX-webapi-X.Y.Z-linux.x86_64.rpm This package contains a Web API.
C library package griddb-XX-c_lib-X.Y.Z-linux.x86_64.rpm This package contains a C header file (/usr/include/gridstore.h) and a library (/usr/lib64/
Java library package griddb-XX-java_lib-X.Y.Z-linux.x86_64.rpm This package contains a Java library (/usr/share/java/gridstore.jar).
Python library package griddb-XX-python_lib-X.Y.Z-linux.x86_64.rpm This package contains a Python package (griddb_python).
Node.js library package griddb-XX-nodejs_lib-X.Y.Z-linux.x86_64.rpm This package contains a Node.js module (griddb_node).
Go library package griddb-XX-go_lib-X.Y.Z-linux.x86_64.rpm This package contains a Go package (griddb/go_client).
NewSQL package griddb-XX-newsql-X.Y.Z-linux.x86_64.rpm This package is provided only for GridDB AE. It contains a JDBC driver.

XX : Edition name(se/ae)

X.Y.Z : Release version

To find out the installation method, see the following manual. "GridDB quick start guide (GridDB_QuickStartGuide.html)"


6 GridDB manuals

GridDB manuals are as follows.

Manual Target Description
GridDB Quick Start Guide Users using GridDB for the first time This manual describes overview, functions and basic operations of GridDB.
GridDB Database Administrators Guide Infrastructure designer
Operations manager
This manual describes the physical design and operation of the database.
GridDB Programming Guide Application developer This manual explains how to use Java and C language APIs using example programs such as data registration and search.
GridDB Advanced Edition SQL Tuning Guide Application developer This manual describes SQL tuning procedures and SQL optimization rules.


7 Dealing with problems

If there are any problems in using GridDB, see the following manual. "GridDB Features Reference (GridDB_FeaturesReference.html)" "GridDB Error Codes (GridDB_ErrorCodes.html)"


8 Important notes and limitations

This section describes about important notes and limitations for using GridDB. The items which should be confirmed and understood to use this product are written here.


8.1 Important notes

No Title Description
1 Compatibility (database) (GridDB SE/GridDB AE) It is not possible to use databases of GridDB V3.5 or earlier versions in GridDB V4.0 or later.
Data migration by export/import tools is required for this case.
To consult the migration, contact the support service representative.
2 Cluster with different major versions of GridDB nodes is not permitted The cluster must be consisted of only the same major version of GridDB nodes in V4.1.1 or later.
Note that different major versions of GridDB nodes are not mixed in the network.
Further in GridDB V3.5 or earlier versions, different major and minor versions of GridDB nodes cannot be mixed in a cluster.
3 Compatibility (Zip output format in exporting) It is not possible to use zip files exported before V2.7 in V2.7 or newer version.
4 Column type in GridDB AE Following data types of GridDB SE are not supported for the columns of table in GridDB AE.
- Geometry (GEOMETRY) type
- Array type
5 SQL in GridDB AE To handle data types and sequences in a query flexibly, there are the cases where their error is not detected in GridDB AE.
6 Compatibility (nodes in a cluster, API and a cluster) - Version compatibility among nodes in a cluster
It is not possible to configure a cluster with mixing V4.1.0 or earlier and V4.1.1 or later nodes. So the rolling update can not be used to migrate from V4.1.0 or earlier.

- Version compatibility of API and a cluster
It is not possible to access a cluster of V4.0.2 or later with NoSQL API library of V4.0.0. The API library used in the application must be replaced to the library of V4.0.2 or later. API is compatible between versions, so there is no need to change the application.


8.2 Limitations

No Title Description
S30007 Database names and user names are case-sensitive in some operations In the operations for the creation, uppercase and lowercase characters are identified as the same. But in operations for the connection, reference and deletion, the names are treated as case-sensitive.

* After creating a database "dbTest", the database named "DBTEST" or "dbtest" cannot be created.
-> In creating a database, the database names different only in uppercase and lowercase characters are identified as the same name.

* The database "dbTest" is not deleted by specifying "DBTEST" or "dbtest". It is required to specify "dbTest" in order to delete the database.
-> In deleting a database, the database names different in uppercase and lowercase characters are identified as different names.
S30009 Empty geometry values can not be registered An error occurs when registering empty geometry value.
Examples of empty geometry data:
S30014 Table partitioning cannot be performed on the table to which the node affinity is set Creating a table by specifying both the node affinity and the partitioning causes an error.
Example) CREATE TABLE table1@affinity(id integer) PARTITION BY HASH(id) PARTITIONS 5
I40004 If columns are added with putContainer of the NoSQL API, the NULL value is set in the corresponding columns of existing rows. The empty value is set until V4.0.3. It will become selectable from the empty value and the NULL value in the future version.
T30004 In case of failure, gs_admin may not be able to get container information When a part of partitions cannot be accessed for a database failure, gs_admin cannot get container information. Even in that case, gs_sh can get the container information on the normal partitions.
T30006 Clusters, databases and containers which name contains any special characters ('-', '.', '/', '=') cannot be handled by the Web API When specifying a cluster name, a database name or a container causes an error.


9 Notices

Basic support contract is required for the use of perpetual license. Please make the basic support contract at the same time of purchasing this product. It is not possible to contract the support service after the purchasing.


10 Trademarks


11 Supplementary explanation

The information about software and its license used by GridDB is included in Readme_en.txt bundled in the server package and the install media.

Contact the representative of the basic support service if there are any inquiries to use this product.


          Copyright Toshiba Digital Solutions Corporation 2017-2019