{"id":46570,"date":"2018-05-30T00:00:00","date_gmt":"2018-05-30T07:00:00","guid":{"rendered":"https:\/\/griddb-linux-hte8hndjf8cka8ht.westus-01.azurewebsites.net\/blog\/griddb-community-edition-version-4-0\/"},"modified":"2025-11-13T12:54:36","modified_gmt":"2025-11-13T20:54:36","slug":"griddb-community-edition-version-4-0","status":"publish","type":"post","link":"https:\/\/griddb-linux-hte8hndjf8cka8ht.westus-01.azurewebsites.net\/en\/blog\/griddb-community-edition-version-4-0\/","title":{"rendered":"GridDB Community Edition Version 4.0"},"content":{"rendered":"

An update for GridDB Community Edition has been released. Version 4.0<\/a> brings with it both practical and convenience features including allowing for a wider breadth of characters in container and cluster names. This release also offers increased maximum data size per node.<\/p>\n

In many NoSQL databases, the maximum data size per node is generally within several TBs; with this update, GridDB can now store up 50 TBs per node. While the number of nodes in a cluster are generally used to aide with redundancy and fault tolerance, there comes a point where those parameters are sufficient and adding more nodes simply for storage space adds needless complexity. It is in these circumstances where a higher data per node capacity can help manage large clusters.<\/p>\n

In addition to allowing larger capacities on a per node basis, version 4.0 also brings with it “Partial Execution Mode” for querying results. To put it simply, this function will allow very large query results to be divided into smaller chunks, ensuring that the buffer size used for sending and receiving the query results stay within a certain range. This means database administrators can feel comfortable running extremely large queries without fear of resources dissipating.<\/p>\n

As mentioned earlier, the use of special characters are now functional when naming containers\/clusters. These characters include: hyphen ‘-‘, dot ‘.’, slash ‘\/’, equal ‘=’. This QOL improvement means migrating from other NoSQL Databases will be a bit easier as renaming your familiar clusters will no longer be a concern.<\/\n\n

><\/p>\n

The last major change that will be previewed is the ability to deallocate unused data blocks. This feature allows DBAs to reduce disk space by removing checkpoint files using Linux file block deallocation processing. For example, if the GridDB cluster recently had a large amount of data deleted manually, or if the DB needs to sit for awhile with no planned updates but with a long-term view on how long the data needs to exist, or the DB simply needs to reduce its size, running the deallocation option is the proper choice. It will remove unused checkpoint files until there is a data update, helping reduce unnecessary disk space.
\nGridDB Community Edition is free and open source. This update can be downloaded right now via our download page or by going directly to Github.<\/p>\n

As a brief summary, here’s a quick list of the features being introduced by this update:<\/p>\n