TimechoDB v0.13.4.1/v1.0.1.1 version has been released! This version is compatible with Apache IoTDB v0.13.4 and v1.0.1, and includes updates to TimechoDB's audit log feature, client whitelist control, whitelist query/modification, and license interface viewing, as well as updates to the Timecho authorization activation process.

Please refer to the contact information at the end to get in touch with Timecho and learn more about the detailed version information!

Highlights of the Release

Highlight 1

Added audit log and document indexing features to TimechoDB. The audit log serves as a record of all the CRUD operations (create, read, update, delete) in the database to ensure information security. The audit log can be configured to record based on criteria such as the source of the operation (manual or system-level write operation).

All operations in TimechoDB are recorded in the PlanExecutor. The execution logs in PlanExecutor are categorized into DDL, DML, and QUERY based on their types. The AuditLogUtils utility class is used to configure and match the specific category for recording audit logs. The related configuration options are as follows:

####################
### Audit log Configuration
####################

# whether to enable the audit log.
# Datatype: Boolean
# enable_audit_log=false

# Output location of audit logs
# Datatype: String
# IOTDB: the stored time series is: root.__system.audit._{user}
# LOGGER: log_audit.log in the log directory
# audit_log_storage=IOTDB,LOGGER

# whether enable audit log for DML operation of data
# whether enable audit log for DDL operation of schema
# whether enable audit log for QUERY operation of data and schema
# Datatype: String
# audit_log_operation=DML,DDL,QUERY

# whether the local write api records audit logs
# Datatype: Boolean
# This contains Session insert api: insertRecord(s), insertTablet(s),insertRecordsOfOneDevice
# MQTT insert api
# RestAPI insert api
# This parameter will cover the DML in audit_log_operation
# enable_audit_log_for_native_insert_api=true

Highlight 2

Added client whitelist control to TimechoDB, allowing you to specify which client addresses are allowed to connect to TimechoDB. To enable whitelist functionality, run the following command:

# Enable whitelist functionality
enable_white_list=true

To specify which IP addresses can connect to TimechoDB, run the following command:

# Support comments
# Support exact matching, one IP per line
10.2.3.4

# Support * wildcard, one IP per line
10.*.1.3
10.100.0.*

Highlight 3

TimechoDB client introduces the following interfaces to support whitelist query/modification and TimechoDB license information query. The TimechoDB client includes all interfaces of the open-source Apache IoTDB client and adds new functional interfaces beyond them.

WhiteListInfoResp getWhiteIpSet() throws IoTDBConnectionException, StatementExecutionException;

void updateWhiteList(Set<String> ipSet)
    throws IoTDBConnectionException, StatementExecutionException;

LicenseInfoResp getLicenseInfo() throws StatementExecutionException, IoTDBConnectionException;

Highlight 4

Added TimechoDB authorization activation mechanism. Execute the script below and copy the relevant code from the console. After generating the activation code based on the machine code, enter it in the console to start TimechoDB:

sudo sbin/start-activate.sh

About Timecho

Founded by the creators of Apache IoTDB, an international top level open source project, Timecho delivers IoT-native time-series solutions with high throughput, high compression, and high availability, assisting industrial users in addressing the challenges of data storage, retrieval, and utilization. We are dedicated to empowering companies to leverage the value of their data with higher reliability at lower cost.

Contact us

E-mail: contact@timecho.com

Homepage: www.timecho.com, www.timecho-global.com