[jira] [Created] (IOTDB-4537) Performance Test for Trigger
liaolanyu created IOTDB-4537: Summary: Performance Test for Trigger Key: IOTDB-4537 URL: https://issues.apache.org/jira/browse/IOTDB-4537 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu The output of this Jira will be a Performance Test Doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4536) Add Trigger Example
liaolanyu created IOTDB-4536: Summary: Add Trigger Example Key: IOTDB-4536 URL: https://issues.apache.org/jira/browse/IOTDB-4536 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4533) [load]An unexpected folder is added
FengQingxin created IOTDB-4533: -- Summary: [load]An unexpected folder is added Key: IOTDB-4533 URL: https://issues.apache.org/jira/browse/IOTDB-4533 Project: Apache IoTDB Issue Type: Bug Components: Core/Others Affects Versions: 0.14.0-SNAPSHOT Reporter: FengQingxin Attachments: image-2022-09-27-14-36-41-625.png An unexpected folder is added !image-2022-09-27-14-36-41-625.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4533) [load]An unexpected folder is added
[ https://issues.apache.org/jira/browse/IOTDB-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] FengQingxin reassigned IOTDB-4533: -- Assignee: yusicheng > [load]An unexpected folder is added > --- > > Key: IOTDB-4533 > URL: https://issues.apache.org/jira/browse/IOTDB-4533 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Others >Affects Versions: 0.14.0-SNAPSHOT >Reporter: FengQingxin >Assignee: yusicheng >Priority: Minor > Attachments: image-2022-09-27-14-36-41-625.png > > > An unexpected folder is added > !image-2022-09-27-14-36-41-625.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4535) Trigger User Doc
liaolanyu created IOTDB-4535: Summary: Trigger User Doc Key: IOTDB-4535 URL: https://issues.apache.org/jira/browse/IOTDB-4535 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4534) Add ITs and UTs for Trigger Execution
liaolanyu created IOTDB-4534: Summary: Add ITs and UTs for Trigger Execution Key: IOTDB-4534 URL: https://issues.apache.org/jira/browse/IOTDB-4534 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4532) Add ITs and UTs for Trigger Management
liaolanyu created IOTDB-4532: Summary: Add ITs and UTs for Trigger Management Key: IOTDB-4532 URL: https://issues.apache.org/jira/browse/IOTDB-4532 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-bin-resources] qiaojialin merged pull request #38: Add pics about template lifetime
qiaojialin merged PR #38: URL: https://github.com/apache/iotdb-bin-resources/pull/38 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-4531) [cluster]Mount template must create the storage group path in advance
xiaozhihong created IOTDB-4531: -- Summary: [cluster]Mount template must create the storage group path in advance Key: IOTDB-4531 URL: https://issues.apache.org/jira/browse/IOTDB-4531 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager, mpp-cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: xiaozhihong Assignee: Yukun Zhou Attachments: image-2022-09-27-11-55-08-955.png In 0.13.X version, when the template is mounted, the storage group path is automatically created by default, In 0.14.X version, when mounting a template, the premise is that there is a created storage group path. Therefore, need to add notes in UserGuide to tell users. !image-2022-09-27-11-55-08-955.png|width=656,height=222! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4530) RestAPi datatype cast error
[
https://issues.apache.org/jira/browse/IOTDB-4530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haonan Hou reassigned IOTDB-4530:
-
Assignee: Zhijia Cao
> RestAPi datatype cast error
> ---
>
> Key: IOTDB-4530
> URL: https://issues.apache.org/jira/browse/IOTDB-4530
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.13.2
>Reporter: Haonan Hou
>Assignee: Zhijia Cao
>Priority: Minor
>
> {code:java}
> curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290"
> -X POST --data
> '{"timestamps":[1635232143960],"measurements":["s1"],"dataTypes":["FLOAT"],"values":[[30650]],"isAligned":false,"deviceId":"root.sg.d1"}'
> http://127.0.0.1:18080/rest/v1/insertTablet{code}
> {code:java}
> {"code":400,"message":"java.lang.Integer cannot be cast to
> java.lang.Double"}{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4530) RestAPi datatype cast error
Haonan Hou created IOTDB-4530:
-
Summary: RestAPi datatype cast error
Key: IOTDB-4530
URL: https://issues.apache.org/jira/browse/IOTDB-4530
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.13.2
Reporter: Haonan Hou
{code:java}
curl -H "Content-Type:application/json" -H "Authorization:Basic cm9vdDpyb290"
-X POST --data
'{"timestamps":[1635232143960],"measurements":["s1"],"dataTypes":["FLOAT"],"values":[[30650]],"isAligned":false,"deviceId":"root.sg.d1"}'
http://127.0.0.1:18080/rest/v1/insertTablet{code}
{code:java}
{"code":400,"message":"java.lang.Integer cannot be cast to
java.lang.Double"}{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4526) [ remove datanode ] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 - change region DataRegion[xx] leader failed
[
https://issues.apache.org/jira/browse/IOTDB-4526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609813#comment-17609813
]
Jinrui Zhang commented on IOTDB-4526:
-
The exception won't lead to failure of DataRegion Migration.
According to the log, the data regions migration succeeded finally, although it
costed much time.
This PR is used to fix the exception
https://github.com/apache/iotdb/pull/7449/files
> [ remove datanode ] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 -
> change region DataRegion[xx] leader failed
> ---
>
> Key: IOTDB-4526
> URL: https://issues.apache.org/jira/browse/IOTDB-4526
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Jinrui Zhang
>Priority: Major
> Attachments: image-2022-09-27-09-54-40-156.png, more_dev.conf,
> screenshot-1.png
>
>
> m_0924_04d9a4a
> schemaregion : ratis
> dataregion :multiLeader
> 均3副本，3C3D，bm写入完成（5万dev，600 sensor / dev , 1万points/sensor），增加2个节点ip75，ip76
> ，再缩容ip72，{color:#DE350B}change region DataRegion[xx] leader failed{color}；new
> peer的data/consensus/data_region 文件夹大（{color:#DE350B}需确认是否正常{color}）；ip72
> 开始removing后还有新的compaction操作（{color:#DE350B}需确认是否必要{color}）。
> ip72 datanode error：
> 2022-09-27 09:33:37,558 [pool-21-IoTDB-DataNodeInternalRPC-Processor-150]
> ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 -{color:#DE350B}
> change region DataRegion[13] leader failed{color}
> 2022-09-27 09:33:37,562 [pool-21-IoTDB-DataNodeInternalRPC-Processor-150]
> ERROR o.a.t.ProcessFunction:47 - Internal error processing changeRegionLeader
> {color:#DE350B}java.lang.NullPointerException: null{color}
> at
> org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.transferLeader(DataNodeInternalRPCServiceImpl.java:808)
> at
> org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.changeRegionLeader(DataNodeInternalRPCServiceImpl.java:790)
> at
> org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3212)
> at
> org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3192)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> ip72（leader）confignode error：
> 2022-09-27 09:33:37,585 [ProcExecWorker-8] ERROR
> o.a.i.c.c.s.d.SyncDataNodeClientPool:147 - Change regions leader error on
> Date node: TEndPoint(ip:192.168.10.72, port:9003)
> org.apache.thrift.TException: Error in calling method changeRegionLeader
> at
> org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:94)
> at
> org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$986af3c1.changeRegionLeader()
> at
> org.apache.iotdb.confignode.client.sync.datanode.SyncDataNodeClientPool.changeRegionLeader(SyncDataNodeClientPool.java:141)
> at
> org.apache.iotdb.confignode.procedure.env.DataNodeRemoveHandler.changeRegionLeader(DataNodeRemoveHandler.java:540)
> at
> org.apache.iotdb.confignode.procedure.impl.RegionMigrateProcedure.executeFromState(RegionMigrateProcedure.java:104)
> at
> org.apache.iotdb.confignode.procedure.impl.RegionMigrateProcedure.executeFromState(RegionMigrateProcedure.java:46)
> at
> org.apache.iotdb.confignode.procedure.StateMachineProcedure.execute(StateMachineProcedure.java:185)
> at
> org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50)
> at
> org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741)
> Caused by: org.apache.thrift.TException: Error in calling method
> recv_changeRegionLeader
> at
> org.apache.iotdb.commons.cl
[jira] [Created] (IOTDB-4529) [Metric] Close active connection in prometheus reporter when metric service stop.
张洪胤 created IOTDB-4529: -- Summary: [Metric] Close active connection in prometheus reporter when metric service stop. Key: IOTDB-4529 URL: https://issues.apache.org/jira/browse/IOTDB-4529 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Assignee: 张洪胤 we need to close active connection in prometheus reporter at the same time when metric service stop. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4525) when the data's size is large ,the IoTDB starts slowly
[ https://issues.apache.org/jira/browse/IOTDB-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4525: -- Assignee: Haiming Zhu > when the data's size is large ,the IoTDB starts slowly > --- > > Key: IOTDB-4525 > URL: https://issues.apache.org/jira/browse/IOTDB-4525 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 刘俊男 >Assignee: Haiming Zhu >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4528) [sync] Pipe operation in cluster version
yanze chen created IOTDB-4528: - Summary: [sync] Pipe operation in cluster version Key: IOTDB-4528 URL: https://issues.apache.org/jira/browse/IOTDB-4528 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yanze chen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4527) Support sql does not contains comma
Jialin Qiao created IOTDB-4527: -- Summary: Support sql does not contains comma Key: IOTDB-4527 URL: https://issues.apache.org/jira/browse/IOTDB-4527 Project: Apache IoTDB Issue Type: Improvement Reporter: Jialin Qiao Assignee: Minghui Liu Currently, we support adding properties in sql, such as: create timeseries root.turbine1.1701.s2 with datatype=FLOAT, encoding=GORILLA, compression=SNAPPY load '' [,sglevel=true/false] We'd better support adding properties without comma. create timeseries root.turbine1.1701.s2 with datatype=FLOAT encoding=GORILLA compression=SNAPPY load '' [sglevel=true/false] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4526) [ remove datanode ] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 - change region DataRegion[xx] leader failed
刘珍 created IOTDB-4526: - Summary: [ remove datanode ] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 - change region DataRegion[xx] leader failed Key: IOTDB-4526 URL: https://issues.apache.org/jira/browse/IOTDB-4526 Project: Apache IoTDB Issue Type: Bug Components: mpp-cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: 刘珍 Assignee: Jinrui Zhang Attachments: image-2022-09-27-09-54-40-156.png m_0924_04d9a4a schemaregion : ratis dataregion :multiLeader 均3副本，3C3D，bm写入完成（5万dev，600 sensor / dev , 1万points/sensor），先增加2个节点ip75，ip76 ，再缩容ip72，缩容失败，ip72 datanode error： 2022-09-27 09:33:37,558 [pool-21-IoTDB-DataNodeInternalRPC-Processor-150] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:806 - change region DataRegion[13] leader failed 2022-09-27 09:33:37,562 [pool-21-IoTDB-DataNodeInternalRPC-Processor-150] ERROR o.a.t.ProcessFunction:47 - Internal error processing changeRegionLeader java.lang.NullPointerException: null at org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.transferLeader(DataNodeInternalRPCServiceImpl.java:808) at org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.changeRegionLeader(DataNodeInternalRPCServiceImpl.java:790) at org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3212) at org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3192) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) ip72（leader）confignode error： 2022-09-27 09:33:37,585 [ProcExecWorker-8] ERROR o.a.i.c.c.s.d.SyncDataNodeClientPool:147 - Change regions leader error on Date node: TEndPoint(ip:192.168.10.72, port:9003) org.apache.thrift.TException: Error in calling method changeRegionLeader at org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:94) at org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$986af3c1.changeRegionLeader() at org.apache.iotdb.confignode.client.sync.datanode.SyncDataNodeClientPool.changeRegionLeader(SyncDataNodeClientPool.java:141) at org.apache.iotdb.confignode.procedure.env.DataNodeRemoveHandler.changeRegionLeader(DataNodeRemoveHandler.java:540) at org.apache.iotdb.confignode.procedure.impl.RegionMigrateProcedure.executeFromState(RegionMigrateProcedure.java:104) at org.apache.iotdb.confignode.procedure.impl.RegionMigrateProcedure.executeFromState(RegionMigrateProcedure.java:46) at org.apache.iotdb.confignode.procedure.StateMachineProcedure.execute(StateMachineProcedure.java:185) at org.apache.iotdb.confignode.procedure.Procedure.doExecute(Procedure.java:365) at org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:414) at org.apache.iotdb.confignode.procedure.ProcedureExecutor.executeProcedure(ProcedureExecutor.java:373) at org.apache.iotdb.confignode.procedure.ProcedureExecutor.access$300(ProcedureExecutor.java:50) at org.apache.iotdb.confignode.procedure.ProcedureExecutor$WorkerThread.run(ProcedureExecutor.java:741) Caused by: org.apache.thrift.TException: Error in calling method recv_changeRegionLeader at org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:94) at org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$986af3c1.recv_changeRegionLeader() at org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Client.changeRegionLeader(IDataNodeRPCService.java:741) at org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$986af3c1.CGLIB$changeRegionLeader$133() at org.apache.iotdb.commons.client.sync.SyncDataNodeInternalServiceClient$$EnhancerByCGLIB$$986af3c1$$FastClassByCGLIB$$bb86de5d.invoke() at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228) at org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:55) ... 11 common frames omitted Caused by: org.apache.thrift.TException: Error in calling method receiveBase at org.apache.iotdb.commons.client.
[jira] [Created] (IOTDB-4525) when the data's size is large ,the IoTDB starts slowly
刘俊男 created IOTDB-4525: -- Summary: when the data's size is large ,the IoTDB starts slowly Key: IOTDB-4525 URL: https://issues.apache.org/jira/browse/IOTDB-4525 Project: Apache IoTDB Issue Type: Bug Reporter: 刘俊男 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4502) Change the IP or Port of the node in Cluster and Restart recovery
[ https://issues.apache.org/jira/browse/IOTDB-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609761#comment-17609761 ] 伊丹翔 commented on IOTDB-4502: 文档：https://apache-iotdb.feishu.cn/docx/doxcn9d2kMsgvgCH5NotNRKoVoQ > Change the IP or Port of the node in Cluster and Restart recovery > - > > Key: IOTDB-4502 > URL: https://issues.apache.org/jira/browse/IOTDB-4502 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: 伊丹翔 >Assignee: 伊丹翔 >Priority: Major > > 集群更改IP或Port重启恢复 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-3818) Support nested expressions in GROUP BY LEVEL
[
https://issues.apache.org/jira/browse/IOTDB-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minghui Liu reassigned IOTDB-3818:
--
Assignee: Minghui Liu
> Support nested expressions in GROUP BY LEVEL
>
>
> Key: IOTDB-3818
> URL: https://issues.apache.org/jira/browse/IOTDB-3818
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: xiaozhihong
>Assignee: Minghui Liu
>Priority: Major
>
> Start 1 confignode and 1 DataNode.
> Nested expressions are not supported in group by level queries, and the
> returned status is incorrect.
> like this：
> {code:java}
> IoTDB> select avg(s1) + avg(s2) from root.sg.* group by level=1;
> Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "select avg(s1) +
> avg(s2) from root.sg.* group by level=1". executeStatement failed. Index 0
> out of bounds for length 0
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4524) Refactor anlyzer for query statement
Minghui Liu created IOTDB-4524: -- Summary: Refactor anlyzer for query statement Key: IOTDB-4524 URL: https://issues.apache.org/jira/browse/IOTDB-4524 Project: Apache IoTDB Issue Type: Task Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch https://apache-iotdb.feishu.cn/docx/doxcnGMGBMDyXk78ZIkprzY8qjb -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4171) Redesign the into clause
[ https://issues.apache.org/jira/browse/IOTDB-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minghui Liu reassigned IOTDB-4171: -- Assignee: Minghui Liu (was: Yuan Tian) > Redesign the into clause > > > Key: IOTDB-4171 > URL: https://issues.apache.org/jira/browse/IOTDB-4171 > Project: Apache IoTDB > Issue Type: Task >Reporter: Yuan Tian >Assignee: Minghui Liu >Priority: Major > > We should redesign the functionality of select into. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4523) [cluster]
xiaozhihong created IOTDB-4523:
--
Summary: [cluster]
Key: IOTDB-4523
URL: https://issues.apache.org/jira/browse/IOTDB-4523
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: xiaozhihong
Assignee: Yongzao Dan
Show that the Region distribution function corresponding to the specified
storage group is not implemented.
Step1: start 3C 3D
Step2: Enter CLI, execute SQL
{code:java}
IoTDB> create timeseries root.sgcc.wf01.d1.wt01 with
datatype=BOOLEAN,encoding=PLAIN
Msg: The statement is executed successfully.
IoTDB> show regions of storage group root.*.wf01
+++--+-+---+-+--++---++
|RegionId|Type|Status|Storage
Group|SeriesSlots|TimeSlots|DataNodeId|Host|RpcPort|Role|
+++--+-+---+-+--++---++
+++--+-+---+-+--++---++
Empty set.
It costs 0.006s
{code}
Refer to:
https://iotdb.apache.org/zh/UserGuide/Master/Maintenance-Tools/Maintenance-Command.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4522) [MultiLeader] Add memory control of queue in multiLeader consensus.
张洪胤 created IOTDB-4522: -- Summary: [MultiLeader] Add memory control of queue in multiLeader consensus. Key: IOTDB-4522 URL: https://issues.apache.org/jira/browse/IOTDB-4522 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 Add memory control of queue in multiLeader consensus. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-bin-resources] HTHou merged pull request #39: Modify time partition example
HTHou merged PR #39: URL: https://github.com/apache/iotdb-bin-resources/pull/39 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
