rename iotdb-engine.properties to iotdb-datanode.properties (apache#6449)

Author: HTHou

README.md

@@ -180,7 +180,7 @@ you run `mvn package` successfully.**
 configuration files are under "conf" folder
 
   * environment config module (`iotdb-env.bat`, `iotdb-env.sh`),
-  * system config module (`iotdb-engine.properties`)
+  * system config module (`iotdb-datanode.properties`)
   * log config module (`logback.xml`).
 
 For more information, please see [Config Manual](https://iotdb.apache.org/UserGuide/Master/Reference/Config-Manual.html).

README_ZH.md

@@ -165,7 +165,7 @@ git checkout vx.x.x
 
 配置文件在"conf"文件夹下
 * 环境配置模块(`iotdb-env.bat`, `iotdb-env.sh`),
-* 系统配置模块(`iotdb-engine.properties`)
+* 系统配置模块(`iotdb-datanode.properties`)
 * 日志配置模块(`logback.xml`)。
 
 有关详细信息，请参见[配置参数](https://iotdb.apache.org/zh/UserGuide/Master/Reference/Config-Manual.html)。

docker/src/main/Dockerfile-single-influxdb

@@ -28,7 +28,7 @@ RUN apt update \
   && unzip /apache-iotdb-*-bin.zip -d / \
   && rm /apache-iotdb-*-bin.zip \
   && mv /apache-iotdb-* /iotdb \
-  && sed -i '/^# enable_influxdb_rpc_service=false/a enable_influxdb_rpc_service=true' /iotdb/sbin/../conf/iotdb-engine.properties \
+  && sed -i '/^# enable_influxdb_rpc_service=false/a enable_influxdb_rpc_service=true' /iotdb/sbin/../conf/iotdb-datanode.properties \
   && apt remove unzip -y \
   && apt autoremove -y \
   && apt purge --auto-remove -y \

docs/Development/HowtoContributeCode.md

@@ -72,11 +72,11 @@ It is required to use "mvn spotless:apply" to format the code before committing,
 
 Notes
 
-1.The default values need to be consistent between iotdb-engine.properties file and IoTDBConfig file.
+1.The default values need to be consistent between iotdb-datanode.properties file and IoTDBConfig file.
 
 2.To modify the configuration parameters, the following files need to be modified 
 
-a.Configuration file: server/src/assembly/resources/conf/iotdb-engine.properties
+a.Configuration file: server/src/assembly/resources/conf/iotdb-datanode.properties
 
 b. Codes: IoTDBDescriptor, IoTDBConfig
 

docs/UserGuide/API/Programming-MQTT.md

@@ -59,7 +59,7 @@ or json array of the above two.
 <img style="width:100%; max-width:800px; max-height:600px; margin-left:auto; margin-right:auto; display:block;" src="https://user-images.githubusercontent.com/6711230/78357469-1bf11880-75e4-11ea-978f-a53996667a0d.png">
 
 ### MQTT Configurations
-The IoTDB MQTT service load configurations from `${IOTDB_HOME}/${IOTDB_CONF}/iotdb-engine.properties` by default.
+The IoTDB MQTT service load configurations from `${IOTDB_HOME}/${IOTDB_CONF}/iotdb-datanode.properties` by default.
 
 Configurations are as follows:
 
@@ -157,7 +157,7 @@ public class CustomizedJsonPayloadFormatter implements PayloadFormatter {
 
     @Override
     public String getName() {
-        // set the value of mqtt_payload_formatter in iotdb-engine.properties as the following string:
+        // set the value of mqtt_payload_formatter in iotdb-datanode.properties as the following string:
         return "CustomizedJson";
     }
 }
@@ -170,8 +170,8 @@ public class CustomizedJsonPayloadFormatter implements PayloadFormatter {
 
 Then, in your server:
 * Create ${IOTDB_HOME}/ext/mqtt/ folder, and put the jar into this folder.
-* Update configuration to enable MQTT service. (`enable_mqtt_service=true` in `conf/iotdb-engine.properties`)
-* Set the value of `mqtt_payload_formatter` in `conf/iotdb-engine.properties` as the value of getName() in your implementation
+* Update configuration to enable MQTT service. (`enable_mqtt_service=true` in `conf/iotdb-datanode.properties`)
+* Set the value of `mqtt_payload_formatter` in `conf/iotdb-datanode.properties` as the value of getName() in your implementation
   , in this example, the value is `CustomizedJson`
 * Launch the IoTDB server.
 * Now IoTDB will use your implementation to parse the MQTT message.

docs/UserGuide/Data-Concept/Data-Type.md

@@ -33,7 +33,7 @@ IoTDB supports the following data types:
 * TEXT (String)
 
 
-The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../Reference/SQL-Reference.md) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](Encoding.md) or [TS\_2DIFF](Encoding.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/Config-Manual.md) in the configuration file `iotdb-engine.properties`.
+The time series of **FLOAT** and **DOUBLE** type can specify (MAX\_POINT\_NUMBER, see [this page](../Reference/SQL-Reference.md) for more information on how to specify), which is the number of digits after the decimal point of the floating point number, if the encoding method is [RLE](Encoding.md) or [TS\_2DIFF](Encoding.md). If MAX\_POINT\_NUMBER is not specified, the system will use [float\_precision](../Reference/Config-Manual.md) in the configuration file `iotdb-datanode.properties`.
 
 * For Float data value, The data range is (-Integer.MAX_VALUE, Integer.MAX_VALUE), rather than Float.MAX_VALUE, and the max_point_number is 19, caused by the limition of function Math.round(float) in Java.
 * For Double data value, The data range is (-Long.MAX_VALUE, Long.MAX_VALUE), rather than Double.MAX_VALUE, and the max_point_number is 19, caused by the limition of function Math.round(double) in Java (Long.MAX_VALUE=9.22E18).

docs/UserGuide/Data-Modeling/SchemaRegion-rocksdb.md

@@ -37,7 +37,7 @@ After that, you can get a **conf** directory and a **lib** directory in
 schema-engine-rocksdb/target/schema-engine-rocksdb. Copy the file in the conf directory to the conf directory of server,
 and copy the files in the lib directory to the lib directory of server.
 
-Then, open the **iotdb-engine.properties** in the conf directory of server, and set the `schema_engine_mode` to
+Then, open the **iotdb-datanode.properties** in the conf directory of server, and set the `schema_engine_mode` to
 Rocksdb_based. Restart the IoTDB, the system will use `RSchemaRegion` to manage the metadata.
 
 ```

docs/UserGuide/Ecosystem Integration/Writing Data on HDFS.md

@@ -41,7 +41,7 @@ Build server and Hadoop module by: `mvn clean package -pl server,hadoop -am -Dma
 
 Then, copy the target jar of Hadoop module `hadoop-tsfile-X.X.X-jar-with-dependencies.jar` into server target lib folder `.../server/target/iotdb-server-X.X.X/lib`.
 
-Edit user config in `iotdb-engine.properties`. Related configurations are:
+Edit user config in `iotdb-datanode.properties`. Related configurations are:
 
 * tsfile\_storage\_fs
 

docs/UserGuide/Maintenance-Tools/Monitor-and-Log-Tools.md

@@ -49,7 +49,7 @@ To grasp the performance of iotdb, this module is added to count the time-consum
 
 #### Configuration parameter
 
-location：conf/iotdb-engine.properties
+location：conf/iotdb-datanode.properties
 
 <center>
 

docs/UserGuide/Maintenance-Tools/Sync-Tool.md

@@ -287,7 +287,7 @@ IoTDB> SHOW PIPESERVER STATUS
 
 ##### **Receiver**
 
-- `vi conf/iotdb-engine.properties`  to config the parameters，set the IP white list to 192.168.0.1/1 to receive and only receive data from sender.
+- `vi conf/iotdb-datanode.properties`  to config the parameters，set the IP white list to 192.168.0.1/1 to receive and only receive data from sender.
 
 ```
 ####################
@@ -420,7 +420,7 @@ It costs 0.134s
   ```
 
   - Cause by: The receiver is not started or the receiver cannot be connected.
-  - Solution: Execute `SHOW PIPESERVER` on the receiver side to check if the receiver side is started, if not use `START PIPESERVER` to start; check if the whitelist in `iotdb-engine.properties` on the receiver side contains the sender ip.
+  - Solution: Execute `SHOW PIPESERVER` on the receiver side to check if the receiver side is started, if not use `START PIPESERVER` to start; check if the whitelist in `iotdb-datanode.properties` on the receiver side contains the sender ip.
 
 - Execute