[jira] [Assigned] (IOTDB-2886) Rename LocalConfigManager to LocalConfigNode and refactor the management of SchemaRegion

2022-04-11 Thread Jira


 [ 
https://issues.apache.org/jira/browse/IOTDB-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

张洪胤 reassigned IOTDB-2886:
--

Assignee: 张洪胤  (was: Yukun Zhou)

> Rename LocalConfigManager to LocalConfigNode and refactor the management of 
> SchemaRegion
> 
>
> Key: IOTDB-2886
> URL: https://issues.apache.org/jira/browse/IOTDB-2886
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: Yukun Zhou
>Assignee: 张洪胤
>Priority: Major
> Fix For: master branch
>
> Attachments: image-2022-04-12-11-03-47-251.png
>
>
> # rename LocalConfigManager to LocalConfigNode
>  # refactor the management of SchemaRegion, the LocalConfigNode only manage 
> schemaRegionId rather than schemaRegion; SchemaRegion is managed by 
> SchemaEngine
>  # fix the CI problems occurred when clear schema  
> !image-2022-04-12-11-03-47-251.png!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2887) Schema Recover Test bug in non and partial memory mode

2022-04-11 Thread Yukun Zhou (Jira)
Yukun Zhou created IOTDB-2887:
-

 Summary: Schema Recover Test bug in non and partial memory mode 
 Key: IOTDB-2887
 URL: https://issues.apache.org/jira/browse/IOTDB-2887
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yukun Zhou
Assignee: Yukun Zhou
 Fix For: master branch
 Attachments: image-2022-04-12-11-52-36-842.png, 
image-2022-04-12-11-53-12-378.png

https://github.com/apache/iotdb/runs/5982679834?check_suite_focus=true

!image-2022-04-12-11-52-36-842.png!

https://github.com/apache/iotdb/runs/5970756756?check_suite_focus=true

!image-2022-04-12-11-53-12-378.png!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2886) Rename LocalConfigManager to LocalConfigNode and refactor the management of SchemaRegion

2022-04-11 Thread Yukun Zhou (Jira)
Yukun Zhou created IOTDB-2886:
-

 Summary: Rename LocalConfigManager to LocalConfigNode and refactor 
the management of SchemaRegion
 Key: IOTDB-2886
 URL: https://issues.apache.org/jira/browse/IOTDB-2886
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yukun Zhou
Assignee: Yukun Zhou
 Fix For: master branch
 Attachments: image-2022-04-12-11-03-47-251.png

# rename LocalConfigManager to LocalConfigNode
 # refactor the management of SchemaRegion, the LocalConfigNode only manage 
schemaRegionId rather than schemaRegion; SchemaRegion is manageed by 
SchemaEngine
 # fix the CI problems occurred when clear schema  

!image-2022-04-12-11-03-47-251.png!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2885) isLeader bug on standalone ratis consensus protocol

2022-04-11 Thread Yongzao Dan (Jira)
Yongzao Dan created IOTDB-2885:
--

 Summary: isLeader bug on standalone ratis consensus protocol
 Key: IOTDB-2885
 URL: https://issues.apache.org/jira/browse/IOTDB-2885
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: Yongzao Dan
Assignee: Song Ziyang


I'm testing isLeader and getLeader interfaces of ratis consensus 
implementation. But the isLeader returns that the standalone ConfigNode is not 
the leader while the getLeader returns the Endpoint of the standalone 
ConfigNode. I suppose that it might be a special situation of raft protocol. 
Please check it~



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2884) Improve SchemaRegion recover when using SchemaFile

2022-04-11 Thread Yukun Zhou (Jira)
Yukun Zhou created IOTDB-2884:
-

 Summary: Improve SchemaRegion recover when using SchemaFile
 Key: IOTDB-2884
 URL: https://issues.apache.org/jira/browse/IOTDB-2884
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yukun Zhou
Assignee: Yukun Zhou
 Fix For: master branch, 0.14.0-SNAPSHOT


Currently, the recover of schemaRegion is only based on mlog. When using 
SchemaFile, the schemaRegion should be able to recover from SchemaFile and 
pre-load part of MTree into memory to support query.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (IOTDB-2883) Speed up creation of timeseries

2022-04-11 Thread Yukun Zhou (Jira)


 [ 
https://issues.apache.org/jira/browse/IOTDB-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yukun Zhou reassigned IOTDB-2883:
-

Assignee: Yukun Zhou

> Speed up creation of timeseries
> ---
>
> Key: IOTDB-2883
> URL: https://issues.apache.org/jira/browse/IOTDB-2883
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: Yukun Zhou
>Assignee: Yukun Zhou
>Priority: Major
> Fix For: master branch, 0.14.0-SNAPSHOT
>
>
> Since we split schema storage into different schemaRegion, we split one mlog 
> of old versions into several mlogs and one schema region take one mlog.
> The cost of scheduled force operation of mlog is expanded, which makes the 
> performance of timeseries creation decrease 15%。



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2883) Speed up creation of timeseries

2022-04-11 Thread Yukun Zhou (Jira)
Yukun Zhou created IOTDB-2883:
-

 Summary: Speed up creation of timeseries
 Key: IOTDB-2883
 URL: https://issues.apache.org/jira/browse/IOTDB-2883
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yukun Zhou
 Fix For: master branch, 0.14.0-SNAPSHOT


Since we split schema storage into different schemaRegion, we split one mlog of 
old versions into several mlogs and one schema region take one mlog.

The cost of scheduled force operation of mlog is expanded, which makes the 
performance of timeseries creation decrease 15%。



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2882) schema display error

2022-04-11 Thread Xi Zhang (Jira)
Xi Zhang created IOTDB-2882:
---

 Summary: schema display error
 Key: IOTDB-2882
 URL: https://issues.apache.org/jira/browse/IOTDB-2882
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Query
Reporter: Xi Zhang
Assignee: Xi Zhang
 Attachments: schema_error.jpg

Display of the uniary expression for the query result may be wrong.

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)