[IOTDB-1672] Separate AlignedInsertPlan from current InsertPlan

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.13.0
• Component/s: Core/Query, Core/Schema Manager, Core/Server
• Labels: pull-request-available
• Sprint: 2021-10-DragonGate
• Assignee: Kaifeng Xue
• Reporter: Yukun Zhou
• Created: 13/Sep/21 02:07
• Updated: 08/Nov/21 07:54
• Resolved: 04/Nov/21 09:46

Description

IoTDB support timeseries and aligned timeseries, in other words, unary measurement and vector measurement.

Currently, the insert plans of these two types of timeseries is distinguished by a "boolean isAligned" field and share the same interface and code. Thus the related code will be confusing and difficult to understand.

For example. While MManager is processing the InsertPlan, the path and measurement list provided by the plan represent different meaning.

1. While process unary measurement, the prefix path means the entity path and the measurement list represents different measurement of target timeseries.
2. While process vector measurement, the prefix path represents the aligned timeseries path and the measurement list represents the sub measurement of target aligned timeseries. 

 

Thus, it's better to process aligned timeseries insert plan individually and the code will be more understandable.

Issue Links

• links to: GitHub Pull Request #4313
• links to: GitHub Pull Request #4318
• links to: GitHub Pull Request #4333