New Features of infobright 4.5

Compared with version 4.5, infobright 4.0 adds a series of features. Let me explain several important improvements.
1. The default log output level can be dynamically adjusted.
If you want to adjust the default level, you have to set it in the configuration file (brighthouse. INI) and restart the infobright server. This is inconvenient. You cannot view the detailed execution plan of related SQL statements and the detailed usage of system resources in a timely manner.

IB>show variables like '%control%';+---------------------------------+-------+| Variable_name                   | Value |+---------------------------------+-------+| brighthouse_ini_controlmessages | 5     |+---------------------------------+-------+1 row in set (0.00 sec)IB>set global brighthouse_ini_controlmessages=1;Query OK, 0 rows affected (0.00 sec)IB>show variables like '%control%';+---------------------------------+-------+| Variable_name                   | Value |+---------------------------------+-------+| brighthouse_ini_controlmessages | 1     |+---------------------------------+-------+1 row in set (0.00 sec)

The larger the value, the more comprehensive the information involved in the execution plan log.

2. reorganize the knowledge grid.
Anyone who has used infobright may know that infobright has a unique index structure similar to that of a row-type database. Its internal name is known as the knowledge grid, which has been resident in the memory to improve query efficiency. We know that when we add, delete, modify, and write data to the table itself, the information in the knowledge grid is also incomplete, which seriously affects the query performance, because at this time, you must read the disk and decompress it to obtain the relevant results. In versions 4.0 and earlier, if you want to regenerate a complete knowledge grid, you must re-import the data. This operation is annoying, and is a waste of time and resources. Starting from version 4.5, You can dynamically adjust only the grid.

[root@IB-centos ~]# icm --rebuild-kns --datadir /usr/local/infobright/data --database test2013-08-21 10:12:16 Infobright Consistency Manager started.For database: 'test',  table: 't1'  Test of table metadata consistency ... [ PASS ]  Test of knowledge grid format for column: id  ... [ PASS ]  Test of knowledge grid consistency for column: id  ... [ PASS ]

Here I only reset the knowledge grid of the test database. ICM is a powerful tool that comes with infobright. It can do many things. Here we only demonstrate that resetting is just a grid. Let's develop it on your own.

3. Changes to DLP verification rules.

DLP is a powerful tool that can import 3 TB data every hour. The character verification rules only support * _ bin. Currently, all verification rules are supported. That is to say, we do not have to modify the validation rules for each table to adapt to DLP.