[IOTDB-1925] Fix the modification of max_select_unseq_file_num_in_each_compaction parameter does not take effect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.12.2
• Fix Version/s: 0.12.3
• Labels: pull-request-available
• Sprint: 2021-10-DragonGate
• Assignee: Liuxuxin
• Reporter: Liuxuxin
• Created: 04/Nov/21 05:56
• Updated: 04/Nov/21 10:57
• Resolved: 04/Nov/21 10:27

Description

1. Description
   No matter how much we modify the value of parameter max_select_unseq_file_num_in_each_unseq_compaction in the configuration file, its value is always 2000 (default value) when IoTDB starts.
2. Cause
   When IoTDBDescriptor parsing the configuration file, it uses a wrong key "max_open_file_num_in_each_unseq_compaction" to get the value of this parameter. But the key of this parameter should be "max_select_unseq_file_num_in_each_unseq_compaction"

Issue Links

• links to: GitHub Pull Request #4323
• links to: GitHub Pull Request #4324