[jira] [Created] (IOTDB-5364) Refactor Count TimeSeries Group By Level based on SchemaReader
Yukun Zhou created IOTDB-5364: - Summary: Refactor Count TimeSeries Group By Level based on SchemaReader Key: IOTDB-5364 URL: https://issues.apache.org/jira/browse/IOTDB-5364 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch Currently, the LevelTimeSeriesCountOperator, serving feature "count timeseries group by level", is implemented by invoking SchemaRegion interfaces directly, which is unable to be interrupt and brings burden to SchemaRegion business logic. Since we want SchemaRegion to only provide the basic SchemaReader, we refactor the implementation of LevelTimeSeriesCountOperator to extract the group by and counting logic from SchemaRegion. Based on SchemaReader, it is more flexible to interrupt the process and release resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5356) The display result of show region command will cause confusion
[ https://issues.apache.org/jira/browse/IOTDB-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654844#comment-17654844 ] Gaofei Cao commented on IOTDB-5356: --- “SeriesSlotId” and "TimeSlotId" has changed "SeriesSlotNum" and "TimeSlotNum" now. !image-2023-01-05-15-53-57-000.png|width=843,height=222! > The display result of show region command will cause confusion > -- > > Key: IOTDB-5356 > URL: https://issues.apache.org/jira/browse/IOTDB-5356 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Houliang Qi >Assignee: Gaofei Cao >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > Attachments: image-2023-01-04-16-33-58-097.png, > image-2023-01-04-16-36-02-719.png, image-2023-01-05-15-53-57-000.png > > Original Estimate: 24h > Remaining Estimate: 24h > > In version 1.0, when we use show regions command, the display of the command > may confuse the user. > As shown below, the different schema regions have the same series slot id. > which is inconsistent with code. > !image-2023-01-04-16-36-02-719.png! > !image-2023-01-04-16-33-58-097.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5363) Try to construct InsertTablet from InsertRowsNode to speed up write operation
Jinrui Zhang created IOTDB-5363: --- Summary: Try to construct InsertTablet from InsertRowsNode to speed up write operation Key: IOTDB-5363 URL: https://issues.apache.org/jira/browse/IOTDB-5363 Project: Apache IoTDB Issue Type: Improvement Reporter: Jinrui Zhang Assignee: Haiming Zhu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5282) Add SQL: show variables
[ https://issues.apache.org/jira/browse/IOTDB-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654829#comment-17654829 ] Qingxin Feng commented on IOTDB-5282: - 收到。并且rel1.0分支也做出了修改与master一致。 > Add SQL: show variables > --- > > Key: IOTDB-5282 > URL: https://issues.apache.org/jira/browse/IOTDB-5282 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Attachments: image-2023-01-05-09-51-56-452.png > > > Describe all global configs, > cluster_name > data_replica_factor > ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5326) Add cluster_name parameter
[ https://issues.apache.org/jira/browse/IOTDB-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654828#comment-17654828 ] Qingxin Feng commented on IOTDB-5326: - 嗯，可以作为改善项目考虑考虑。主要就是避免你说的这个不兼容版本被加入集群，导致集群不可用报错。但是究竟哪些小版本的修改会引起这个不兼容（或者bug）目前并没有发现的手段。 > Add cluster_name parameter > -- > > Key: IOTDB-5326 > URL: https://issues.apache.org/jira/browse/IOTDB-5326 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Yongzao Dan >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > > We need the parameter `cluster_name` to distinguish different clusters. > > Add `cluster_name` parameter in iotdb-common.property > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5206) Fix when target file is deleted in Compaction exception handler and recover
[ https://issues.apache.org/jira/browse/IOTDB-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654819#comment-17654819 ] Jinrui Zhang commented on IOTDB-5206: - 执行时策略： [https://apache-iotdb.feishu.cn/docs/doccnOxzotqCdP94MuO1HIDjv4c] 恢复时策略：https://apache-iotdb.feishu.cn/docx/I9yIdIoRgo5dBCxb1Svcoil7nDg#T8UmdA088oY2CwxyAfVcXHUanSh > Fix when target file is deleted in Compaction exception handler and recover > --- > > Key: IOTDB-5206 > URL: https://issues.apache.org/jira/browse/IOTDB-5206 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: master branch, 1.0.0 >Reporter: 周沛辰 >Assignee: 周沛辰 >Priority: Major > Labels: pull-request-available > Original Estimate: 72h > Remaining Estimate: 72h > > *Description* > After compaction, if the target file is empty, its corresponding disk file > will be deleted. If an exception or system interruption occurs, there will be > problems in restart recovery and set allowCompaction to false. > 2022-12-20 09:23:53,086 [pool-12-IoTDB-Recovery-Thread-Pool-1] ERROR > o.a.i.d.e.c.t.CompactionRecoverTask:300 - root.iot-0 > [Compaction][ExceptionHandler] target file > sequence/root.iot/0/0/1670572962795-1051-2-1.inner is not complete, and some > source files is lost, do nothing. Set allowCompaction to false > 2022-12-20 09:23:53,087 [pool-12-IoTDB-Recovery-Thread-Pool-1] ERROR > o.a.i.d.e.c.t.CompactionRecoverTask:133 - root.iot-0 [Compaction][Recover] > Failed to recover compaction, set allowCompaction to false > *Reason* > Empty target files will be deleted in compaction. In recovery, system will > report source files are lost and empty target file has been deleted. > *Solution* > Empty target files are not deleted during the compaction until the end of the > compaction. However, after recovery, the empty target file will not be > deleted, but it will not affect the correctness of the system. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5326) Add cluster_name parameter
[ https://issues.apache.org/jira/browse/IOTDB-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654816#comment-17654816 ] Jialin Qiao commented on IOTDB-5326: 之后如果想实现滚动升级（一个节点一个节点的升级），代码版本还不能要求必须一样。倒是可以加个检查，如果用户多个节点版本不一致，而且我们明显知道不兼容的，就提示用户有问题 > Add cluster_name parameter > -- > > Key: IOTDB-5326 > URL: https://issues.apache.org/jira/browse/IOTDB-5326 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Yongzao Dan >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > > We need the parameter `cluster_name` to distinguish different clusters. > > Add `cluster_name` parameter in iotdb-common.property > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5357) [privilege] show triggers and show functions should require less privileges on timeseries
[ https://issues.apache.org/jira/browse/IOTDB-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuan Tian reassigned IOTDB-5357: Assignee: liaolanyu (was: Yuan Tian) > [privilege] show triggers and show functions should require less privileges > on timeseries > - > > Key: IOTDB-5357 > URL: https://issues.apache.org/jira/browse/IOTDB-5357 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: changxue >Assignee: liaolanyu >Priority: Major > > [privilege] show trigger and show functions should require less privileges on > timeseries > actual result: > "show triggers" and "show functions" require READ privilege on root.**, or it > would return 803. > consider this scenario: > Suppose 2 company share 1 IoTDB service and they own their own databse, now > grant them privileges on root.sg1.** or root.sg2.** and they own different > triggers and UDF. When using show triggers or show functions, they would like > to get different result what the actual triggers or UDFs are rather than an > error with privilage. > expect: > "show triggers" and "show functions" only show the results on the timeseries > which they have READ privilege. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5326) Add cluster_name parameter
[ https://issues.apache.org/jira/browse/IOTDB-5326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654811#comment-17654811 ] Qingxin Feng commented on IOTDB-5326: - 添加节点有没有必要检查代码版本呢？ 比如为了降低管理复杂度，而要求各节点版本一致 > Add cluster_name parameter > -- > > Key: IOTDB-5326 > URL: https://issues.apache.org/jira/browse/IOTDB-5326 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Yongzao Dan >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > > We need the parameter `cluster_name` to distinguish different clusters. > > Add `cluster_name` parameter in iotdb-common.property > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5126) Register using hostname, but appears IP but not hostname when show regions
[ https://issues.apache.org/jira/browse/IOTDB-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654803#comment-17654803 ] changxue commented on IOTDB-5126: - Build: 4d94377 verified. !screenshot-1.png|height=200,width=600! > Register using hostname, but appears IP but not hostname when show regions > -- > > Key: IOTDB-5126 > URL: https://issues.apache.org/jira/browse/IOTDB-5126 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Gaofei Cao >Assignee: 伊丹翔 >Priority: Minor > Labels: pull-request-available > Attachments: image-2022-12-06-10-38-14-966.png, screenshot-1.png > > > !image-2022-12-06-10-38-14-966.png|width=745,height=356! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5090) Npe when stop data node
[ https://issues.apache.org/jira/browse/IOTDB-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654789#comment-17654789 ] changxue commented on IOTDB-5090: - 是在datanode启动失败的时候会有这个bug。启动失败会走停止流程，但这两个Impl只有在启动成功时才会被初始化，所以加了一个npe判断. 我的重现方法： 1. 将集群的一个节点停止 2. 将单机的data替换这个集群节点的data目录 3. start-datanode.sh 结果没有NPE： !screenshot-1.png|width=617,height=237! > Npe when stop data node > --- > > Key: IOTDB-5090 > URL: https://issues.apache.org/jira/browse/IOTDB-5090 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Gaofei Cao >Assignee: 伊丹翔 >Priority: Minor > Labels: pull-request-available > Attachments: image-2022-11-30-16-13-02-229.png, screenshot-1.png > > > !image-2022-11-30-16-13-02-229.png|width=617,height=237! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5362) [ rel/1.0 compaction ]ERROR o.a.i.d.e.c.CompactionUtils:276 - Device is overlapped between file
刘珍 created IOTDB-5362:
-
Summary: [ rel/1.0 compaction ]ERROR
o.a.i.d.e.c.CompactionUtils:276 - Device is overlapped between file
Key: IOTDB-5362
URL: https://issues.apache.org/jira/browse/IOTDB-5362
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 1.0.1
Reporter: 刘珍
Assignee: Jinrui Zhang
有问题的版本：rel/1.0 2023-01-04_f0fcac6
1.关合并，在master 2022-12-07 a0b2c8c版本 生成数据，备份在
私有云1期 172.16.2.4
/data1/iotdb/m_1207_a0b2c8c_fast2/data
顺序：7085 tsfile
乱序：51227 tsfile
2. 把数据copy到/data1/iotdb/r_0104_f0fcac6 进行合并
合并报错：
2023-01-04 16:40:54,766 [pool-43-IoTDB-Compaction-1] ERROR
o.a.i.d.e.c.CompactionUtils:276 - {color:#DE350B}*root.test.g2_0 Device
root.test.g2_0.d_4049 is overlapped between file is
*{color}/data1/iotdb/r_0104_f0fcac6/./sbin/../data/datanode/data/sequence/root.test.g2_0/3/25/1670421517878-236-0-1.tsfile,
status: COMPACTING and file is
/data1/iotdb/r_0104_f0fcac6/./sbin/../data/datanode/data/sequence/root.test.g2_0/3/25/1670421533083-239-2-0.tsfile,
status: CLOSED, end time in file is
/data1/iotdb/r_0104_f0fcac6/./sbin/../data/datanode/data/sequence/root.test.g2_0/3/25/1670421517878-236-0-1.tsfile,
status: COMPACTING is 1535678409000, start time in file is
/data1/iotdb/r_0104_f0fcac6/./sbin/../data/datanode/data/sequence/root.test.g2_0/3/25/1670421533083-239-2-0.tsfile,
status: CLOSED is 153566842
测试环境，私有云1期 172.16.2.4 8C32GB
1. 关合并生成数据备份
master 2022-12-07 a0b2c8c配置参数
ConfigNode
MAX_HEAP_SIZE="2G"
DataNode
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE="6G"
COMMON
time_partition_interval=6048000
avg_series_point_number_threshold=1
enable_seq_space_compaction=false
enable_unseq_space_compaction=false
enable_cross_space_compaction=false
BM 配置见附件。
2. rel/1.0 2023-01-04_f0fcac6
数据库配置
ConfigNode
MAX_HEAP_SIZE="2G"
DataNode
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE="6G"
COMMON
time_partition_interval=6048000
avg_series_point_number_threshold=1
enable_seq_space_compaction=true
enable_unseq_space_compaction=true
enable_cross_space_compaction=true
cross_performer=fast
inner_seq_performer=fast
compaction_io_rate_per_sec=1000
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-5282) Add SQL: show variables
[ https://issues.apache.org/jira/browse/IOTDB-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654761#comment-17654761 ] Gaofei Cao commented on IOTDB-5282: --- `show cluster parameters` has changed to `show variables` > Add SQL: show variables > --- > > Key: IOTDB-5282 > URL: https://issues.apache.org/jira/browse/IOTDB-5282 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Attachments: image-2023-01-05-09-51-56-452.png > > > Describe all global configs, > cluster_name > data_replica_factor > ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5282) Add SQL: show cluster parameter
[ https://issues.apache.org/jira/browse/IOTDB-5282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654700#comment-17654700 ] Qingxin Feng commented on IOTDB-5282: - master分支该命令报错 !image-2023-01-05-09-51-56-452.png|width=1194,height=703! > Add SQL: show cluster parameter > --- > > Key: IOTDB-5282 > URL: https://issues.apache.org/jira/browse/IOTDB-5282 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Attachments: image-2023-01-05-09-51-56-452.png > > > Describe all global configs, > cluster_name > data_replica_factor > ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5361) Refactor device and timeseries count based on SchemaReader
Yukun Zhou created IOTDB-5361: - Summary: Refactor device and timeseries count based on SchemaReader Key: IOTDB-5361 URL: https://issues.apache.org/jira/browse/IOTDB-5361 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5356) The display result of show region command will cause confusion
[ https://issues.apache.org/jira/browse/IOTDB-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-5356: -- Assignee: Gaofei Cao (was: Yongzao Dan) > The display result of show region command will cause confusion > -- > > Key: IOTDB-5356 > URL: https://issues.apache.org/jira/browse/IOTDB-5356 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Houliang Qi >Assignee: Gaofei Cao >Priority: Major > Labels: pull-request-available > Fix For: 1.0.1 > > Attachments: image-2023-01-04-16-33-58-097.png, > image-2023-01-04-16-36-02-719.png > > Original Estimate: 24h > Remaining Estimate: 24h > > In version 1.0, when we use show regions command, the display of the command > may confuse the user. > As shown below, the different schema regions have the same series slot id. > which is inconsistent with code. > !image-2023-01-04-16-36-02-719.png! > !image-2023-01-04-16-33-58-097.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5360) Release node and iterator in AbstractTreeVisitor
yanze chen created IOTDB-5360: - Summary: Release node and iterator in AbstractTreeVisitor Key: IOTDB-5360 URL: https://issues.apache.org/jira/browse/IOTDB-5360 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen To support pin and unpin in SchemaFile mode, AbstractTreeVisitor should release node and iterator after using. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5359) Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset
yanze chen created IOTDB-5359: - Summary: Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset Key: IOTDB-5359 URL: https://issues.apache.org/jira/browse/IOTDB-5359 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5358) dn_data_dir failed to be effectively set when executing load
yusicheng created IOTDB-5358: Summary: dn_data_dir failed to be effectively set when executing load Key: IOTDB-5358 URL: https://issues.apache.org/jira/browse/IOTDB-5358 Project: Apache IoTDB Issue Type: Bug Reporter: yusicheng Assignee: yusicheng Fix For: master branch When the user defines the dn_data_dir, this option will not take effect for the load folder -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4976) [UDF]no error return when the datatype of input timeseries and the UDF are not match in nested query
[
https://issues.apache.org/jira/browse/IOTDB-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654366#comment-17654366
]
liaolanyu commented on IOTDB-4976:
--
The status code is 301.
!image-2023-01-04-17-34-51-103.png!
> [UDF]no error return when the datatype of input timeseries and the UDF are
> not match in nested query
>
>
> Key: IOTDB-4976
> URL: https://issues.apache.org/jira/browse/IOTDB-4976
> Project: Apache IoTDB
> Issue Type: Improvement
>Reporter: changxue
>Assignee: liaolanyu
>Priority: Minor
> Attachments: image-2023-01-04-17-34-51-103.png
>
>
> [UDF]no error return when the datatype of input timeseries and the UDF are
> not match in nested query
> description:
> my_max is a function of getting the max value of int values and only
> processing int value.
> my_sum is a function equals the native function of sum, it outputs double
> value.
> when the double result of my_sum is given to my_max as inputing value, it
> would be error in method transform or terminate. But the exception may be
> catched, the logs of datanode show nothing. *That's the problem.* It's not
> convenient to find the reason for users.
>
> reproduction:
> {code:sql}
> create database root.udf.non_aligned;
> create timeseries root.udf.non_aligned.cl01.temp with datatype=int32;
> create timeseries root.udf.non_aligned.cl01.pressure with datatype=int32;
> insert into root.udf.non_aligned.cl01(time, temp,pressure) values (1, 1850,
> 1800), (3, 2600, 2600), (4, 2300,null),(5, null, 4800),(6, 3500,2300);
> CREATE FUNCTION my_max AS 'Max';
> CREATE FUNCTION my_sum AS "com.timecho.udf.normal.MySum";
> -- this would return 0
> select my_max(my_sum(temp)) from root.udf.non_aligned.cl01;{code}
> messages:
> {code:sql}
> IoTDB> select my_max(my_sum(temp)) from root.udf.non_aligned.cl01;
> +-+--+
> | Time|my_max(my_sum(root.udf.non_aligned.cl01.temp))|
> +-+--+
> |1970-01-01T08:00:00.001+08:00| 0|
> +-+--+
> Total line number = 1
> It costs 0.163s
> IoTDB> select my_sum(temp) from root.udf.non_aligned.cl01;
> +-+--+
> | Time|my_sum(root.udf.non_aligned.cl01.temp)|
> +-+--+
> |1970-01-01T08:00:00.001+08:00| 10250.0|
> +-+--+
> Total line number = 1
> It costs 0.018s {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5357) [privilege] show triggers and show functions should require less privileges on timeseries
changxue created IOTDB-5357: --- Summary: [privilege] show triggers and show functions should require less privileges on timeseries Key: IOTDB-5357 URL: https://issues.apache.org/jira/browse/IOTDB-5357 Project: Apache IoTDB Issue Type: Improvement Reporter: changxue Assignee: Yuan Tian [privilege] show trigger and show functions should require less privileges on timeseries actual result: "show triggers" and "show functions" require READ privilege on root.**, or it would return 803. consider this scenario: Suppose 2 company share 1 IoTDB service and they own their own databse, now grant them privileges on root.sg1.** or root.sg2.** and they own different triggers and UDF. When using show triggers or show functions, they would like to get different result what the actual triggers or UDFs are rather than an error with privilage. expect: "show triggers" and "show functions" only show the results on the timeseries which they have READ privilege. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5356) The display result of show region command will cause confusion
Houliang Qi created IOTDB-5356: -- Summary: The display result of show region command will cause confusion Key: IOTDB-5356 URL: https://issues.apache.org/jira/browse/IOTDB-5356 Project: Apache IoTDB Issue Type: Improvement Components: Core/Engine Reporter: Houliang Qi Attachments: image-2023-01-04-16-33-58-097.png, image-2023-01-04-16-36-02-719.png In version 1.0, when we use show regions command, the display of the command may confuse the user. As shown below, the different schema regions have the same series slot id. which is inconsistent with code. !image-2023-01-04-16-36-02-719.png! !image-2023-01-04-16-33-58-097.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5356) The display result of show region command will cause confusion
[ https://issues.apache.org/jira/browse/IOTDB-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi reassigned IOTDB-5356: -- Assignee: Yongzao Dan > The display result of show region command will cause confusion > -- > > Key: IOTDB-5356 > URL: https://issues.apache.org/jira/browse/IOTDB-5356 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Engine >Reporter: Houliang Qi >Assignee: Yongzao Dan >Priority: Major > Attachments: image-2023-01-04-16-33-58-097.png, > image-2023-01-04-16-36-02-719.png > > > In version 1.0, when we use show regions command, the display of the command > may confuse the user. > As shown below, the different schema regions have the same series slot id. > which is inconsistent with code. > !image-2023-01-04-16-36-02-719.png! > !image-2023-01-04-16-33-58-097.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5355) Log RewriteCrossSpaceCompactionTask increase process
Pengfei Liu created IOTDB-5355: -- Summary: Log RewriteCrossSpaceCompactionTask increase process Key: IOTDB-5355 URL: https://issues.apache.org/jira/browse/IOTDB-5355 Project: Apache IoTDB Issue Type: Improvement Components: Core/Compaction Reporter: Pengfei Liu Assignee: Pengfei Liu Fix For: 0.13.3 Log RewriteCrossSpaceCompactionTask increase process When the interzone compaction task is slow and after the merge process restarts, it is difficult to locate the problem through the logs -- This message was sent by Atlassian Jira (v8.20.10#820010)
