What is New in NDB Cluster The performance of some SQL statements is not noticeably improved by this enhancement, due to the fact that they require scans of table Blob columns, which breaks up batching. Such statements include those of the types listed here: To take advantage of this improvement to its fullest extent, you may wish to increase the values used for the  --ndb-batch-size  and  --ndb-blob-write-batch-bytes  options for  mysqld , to minimize the number of round trips required to modify Blobs. For replication, it is also recommended that you enable the  slave_allow_batching  system variable, which minimizes the number of round trips required by the replica cluster to apply epoch transactions. When taking an NDB Cluster backup, you can encrypt it by using  ENCRYPT PASSWORD= password  with the management client  START BACKUP  command. Users of the MGM API can also initiate an encrypted backup by calling  ndb_mgm_start_backup4() . You can encrypt existing backup files using the  ndbxfrm  utility which is added to the NDB Cluster distribution in the 8.0.22 release; this program can also be employed for decrypting encrypted backup files. In addition,  ndbxfrm  can compress backup files and decompress compressed backup files using the same method that is employed by NDB Cluster for creating backups when the  CompressedBackup configuration parameter is set to 1. To restore from an encrypted backup, use  ndb_restore  with the options  --decrypt  and  --backup- password . Both options are required, along with any others that would be needed to restore the same • Node.js update.   Beginning with with NDB 8.0.22, the  NDB  adapter for Node.js is built using version 12.18.3, and only that version (or a later version of Node.js) is now supported. • Encrypted backups.   NDB 8.0.22 adds support for backup files encrypted using AES-256-CBC; this is intended to protect against recovery of data from backups that have been accessed by unathorized parties. When encrypted, backup data is protected by a user-supplied password. The password can be any string consisting of up to 256 characters from the range of printable ASCII characters other than  ! , ’ ,  " ,  $ ,  % ,  \ , and  ^ . Retention of the password used to encrypt any given NDB Cluster backup must be performed by the user or application;  NDB  does not save the password. The password can be empty, although this is not recommended. • SELECT FROM  table  [WHERE  key_column  IN ( blob_value_list )] , where rows are selected by matching on a primary key or unique key column which uses a Blob type • UPDATE  table  SET  blob_column  =  blob_value  WHERE  condition , using a  condition which does not depend on a unique value • DELETE FROM  table  WHERE  condition  to delete rows containing one or more Blob columns, using a  condition  which does not depend on a unique value •A copying  ALTER TABLE  statement on a table which already used the  NDB  storage engine prior to executing the statement, and whose rows contain one or more Blob columns before or after the statement is executed (or both) 3950