You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Yukun Zhou (Jira)" <ji...@apache.org> on 2021/09/26 09:08:00 UTC
[jira] [Assigned] (IOTDB-1675) Introduce UnaryMeasurementMNode and
VectorMeasurementMNode
[ https://issues.apache.org/jira/browse/IOTDB-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yukun Zhou reassigned IOTDB-1675:
---------------------------------
Assignee: Yukun Zhou
> Introduce UnaryMeasurementMNode and VectorMeasurementMNode
> ----------------------------------------------------------
>
> Key: IOTDB-1675
> URL: https://issues.apache.org/jira/browse/IOTDB-1675
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Schema Manager, Core/Server
> Reporter: Yukun Zhou
> Assignee: Yukun Zhou
> Priority: Major
> Fix For: 0.13.0
>
> Attachments: image-2021-09-13-11-29-04-803.png
>
>
> Currently, unary measurement schema and vector measurement schema is hold by MeasurementMNode. The unary case and vector case is distinguished by schema type check.
> To make the code more clean, it's better to separate the process of two cases into different methods and set specialized param, like UnaryMeasurementMNode and VectorMeasurementMNode, to avoid redundant schema check. And the separation will make the code more explicit and easy to maintain.
> Besides, some features like alias, tag, and trigger do not support vector case for the time being. These should be separated from the unary case for future implementation and extension.
>
> !image-2021-09-13-11-29-04-803.png|width=477,height=299!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)