[jira] [Created] (IOTDB-5229) Some Python test failed
Haonan Hou created IOTDB-5229: - Summary: Some Python test failed Key: IOTDB-5229 URL: https://issues.apache.org/jira/browse/IOTDB-5229 Project: Apache IoTDB Issue Type: Bug Affects Versions: master branch Reporter: Haonan Hou Attachments: image-2022-12-19-09-37-38-464.png !image-2022-12-19-09-37-38-464.png|width=417,height=370! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5229) Some Python test failed
[ https://issues.apache.org/jira/browse/IOTDB-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5229: - Assignee: Haonan Hou > Some Python test failed > --- > > Key: IOTDB-5229 > URL: https://issues.apache.org/jira/browse/IOTDB-5229 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: master branch >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > Attachments: image-2022-12-19-09-37-38-464.png > > > !image-2022-12-19-09-37-38-464.png|width=417,height=370! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4439) Add count window in RawDataAggregationOperator window management framework
[ https://issues.apache.org/jira/browse/IOTDB-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-4439: -- Assignee: yang caiyin (was: Hang Zhang) > Add count window in RawDataAggregationOperator window management framework > -- > > Key: IOTDB-4439 > URL: https://issues.apache.org/jira/browse/IOTDB-4439 > Project: Apache IoTDB > Issue Type: Task >Reporter: Hang Zhang >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5230) LogicPlan for window functions
yang caiyin created IOTDB-5230: -- Summary: LogicPlan for window functions Key: IOTDB-5230 URL: https://issues.apache.org/jira/browse/IOTDB-5230 Project: Apache IoTDB Issue Type: Task Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5231) [monitor]datanode could not start when connecting 9091 error
changxue created IOTDB-5231: --- Summary: [monitor]datanode could not start when connecting 9091 error Key: IOTDB-5231 URL: https://issues.apache.org/jira/browse/IOTDB-5231 Project: Apache IoTDB Issue Type: Bug Affects Versions: 1.0.0 Reporter: changxue Assignee: Hongyin Zhang Attachments: config.tar.gz, monitor_error_log.tar.gz [monitor]datanode could not start when connecting 9091 error environment: 3C3D cluster, rel/1.0 branch 1. enable prometheus monitor 2. the prometheus service has not been started problem: 1. 监控是附加功能,打开它并且它工作不正常(可以warning),但不应该出现error,不应该影响rpc service等的启动。 2. 这种情况下,stop-datanode.sh 是不能成功停止成功的,需要kill {code} 2022-12-19 10:26:23,574 [main] INFO o.a.i.m.AbstractMetricService:130 - Detect more than one MetricManager, will use org.apache.iotdb.metrics.micrometer.MicrometerMetricManager 2022-12-19 10:26:23,574 [main] INFO o.a.i.m.AbstractMetricService:137 - Load metric reporters, type: [PROMETHEUS] 2022-12-19 10:26:23,939 [main] ERROR o.a.i.c.s.m.MetricService:52 - Failed to start Metrics ServerService because: reactor.netty.ChannelBindException: Failed to bind on [0.0.0.0:9091] Suppressed: java.lang.Exception: #block terminated with an error at reactor.core.publisher.BlockingSingleSubscriber.blockingGet(BlockingSingleSubscriber.java:139) at reactor.core.publisher.Mono.block(Mono.java:1731) at reactor.netty.transport.ServerTransport.bindNow(ServerTransport.java:145) at reactor.netty.transport.ServerTransport.bindNow(ServerTransport.java:130) at org.apache.iotdb.metrics.reporter.prometheus.PrometheusReporter.start(PrometheusReporter.java:81) at org.apache.iotdb.metrics.CompositeReporter.startAll(CompositeReporter.java:38) at org.apache.iotdb.metrics.AbstractMetricService.startAllReporter(AbstractMetricService.java:193) at org.apache.iotdb.metrics.AbstractMetricService.startCoreModule(AbstractMetricService.java:98) at org.apache.iotdb.metrics.AbstractMetricService.startService(AbstractMetricService.java:76) at org.apache.iotdb.commons.service.metric.MetricService.start(MetricService.java:49) at org.apache.iotdb.commons.service.RegisterManager.register(RegisterManager.java:51) at org.apache.iotdb.db.service.DataNode.doAddNode(DataNode.java:162) at org.apache.iotdb.db.service.DataNodeServerCommandLine.run(DataNodeServerCommandLine.java:95) at org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58) at org.apache.iotdb.db.service.DataNode.main(DataNode.java:131) 2022-12-19 10:26:23,940 [main] ERROR o.a.i.db.service.DataNode:178 - Fail to start server {code} -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5232) Add Schema Memory Usage metric monitor
Yukun Zhou created IOTDB-5232: - Summary: Add Schema Memory Usage metric monitor Key: IOTDB-5232 URL: https://issues.apache.org/jira/browse/IOTDB-5232 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch, 0.13.4, 1.0.1 The remaining memory for schema module is a critical factor considered for series registering and resource updating. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5233) Correct the message of unsupported thrift interface of schema template
Yukun Zhou created IOTDB-5233: - Summary: Correct the message of unsupported thrift interface of schema template Key: IOTDB-5233 URL: https://issues.apache.org/jira/browse/IOTDB-5233 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Thrift may return TException to client when there's UnsupportedException directly thrown and uncaught in ClientRPCServiceImpl. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5233) Correct the message of unsupported thrift interface of schema template
[ https://issues.apache.org/jira/browse/IOTDB-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yukun Zhou reassigned IOTDB-5233: - Fix Version/s: master branch 1.0.1 Sprint: 2022-12-Schema Assignee: Yukun Zhou > Correct the message of unsupported thrift interface of schema template > -- > > Key: IOTDB-5233 > URL: https://issues.apache.org/jira/browse/IOTDB-5233 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Fix For: master branch, 1.0.1 > > > Thrift may return TException to client when there's UnsupportedException > directly thrown and uncaught in ClientRPCServiceImpl. > Current interfaces need to be fixed are: > sessionPool.addAlignedMeasurementsInTemplate > sessionPool.addAlignedMeasurementInTemplate > sessionPool.addUnalignedMeasurementInTemplate > sessionPool.addUnalignedMeasurementsInTemplate > sessionPool.deleteNodeInTemplate -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5227) docker module improvement
[ https://issues.apache.org/jira/browse/IOTDB-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649128#comment-17649128 ] changxue commented on IOTDB-5227: - Why we need to mount /etc/hosts? Besides, what is the meaning of ":ro"? give the container write permission regarding to /etc/hosts? Is that safe? answer: We make a IoTDB cluster with 3 nodes, so they must know each other, so /etc/hosts is the way to make them know each other. > docker module improvement > - > > Key: IOTDB-5227 > URL: https://issues.apache.org/jira/browse/IOTDB-5227 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Xiangdong Huang >Assignee: changxue >Priority: Major > > in v1.0, current docker module has some issues: > > 1. Readme.md file: > 1.1 no instruction about "The definition of tag "latest"" > 1.2 How to build > Normally, we do not create any temporary folder in the root path. > Therefore, please move "tmp" folder to target/tmp. > Besides, readme should be a "step-by-step" instruction. So, we need to say > how to get release files first (mvn package -DskipTests. or download zip file > from the internet, which IMO is more suggestted, because in this way, we can > make sure the v1.0's docker image has no difference with the released > binaries, and that is why we download zip file from the internet in previous > dockerfile.), and then copy, and then give `docker build` command. > 1.3 How to run IoTDB > "Since 1.0.0, see [offical > documents.|https://iotdb.apache.org/UserGuide/Master/QuickStart/WayToGetIoTDB.html]"; > -> It is better to paste the simplest command here, and then give reference > for complex usage (like what we do now) > > > 2. Website > [https://iotdb.apache.org/UserGuide/Master/QuickStart/WayToGetIoTDB.html] > {code:java} > # get IoTDB official image > docker pull apache/iotdb:1.0.0-1c1d > # create docker bridge network > docker network create --driver=bridge --subnet=172.18.0.0/16 > --gateway=172.18.0.1 iotdb > # create docker container > docker run -d --name iotdb-service \ > --hostname iotdb-service \ > --network iotdb \ > --ip 172.18.0.6 \ > -p 26667:6667 \ > -e cn_internal_address=iotdb-service \ > -e cn_target_config_node_list=iotdb-service:22277 \ > -e dn_rpc_address=iotdb-service \ > -e dn_internal_address=iotdb-service \ > -e dn_target_config_node_list=iotdb-service:22277 \ > apache/iotdb:1.0.0-1c1d > # execute SQL > docker exec -ti iotdb-service /iotdb/sbin/start-cli.sh -h iotdb-service {code} > > a. Why use 26667 port? By default, we'd better keep it the same with port in > the container > b. Why do we need set "network" and "ip" for this simple usage? If we do not > use the network and IP, is that possible to use the following command? > {code:java} > $IOTDB_HOME/sbin/start-cli.sh -h -p 26667 {code} > Besides, which IP here it is? 172.18.0.6? or 127.0.0.1? (I mean, the hoster's > IP or the container's IP) > > c. I notice that in our source code repo, Dockerfile-compose use > "172.20.0.6", why we use "172.18" here? If there is no reason, it is better > to keep consisent. Besides, why we use "*.*.0.6" ip? > > d. If we need to store data, how to mount the volume? still `/iotdb/data` and > `/iotdb/logs` (for log) ? > > 3. Website "Notice:The confignode service would fail when restarting this > container if the IP Adress of the container has been changed." > Is this the reason that we have to claim the IP and network explicitly? If it > is, then put this sentence before the command. > > 4. Website Docker-compose > {code:java} > # docker-compose-1c1d.yml > version: "3" > services: > iotdb-service: > image: apache/iotdb:1.0.0-1c1d > hostname: iotdb-service > container_name: iotdb-service > ports: > - "26667:6667" > environment: > - cn_internal_address=iotdb-service > - cn_target_config_node_list=iotdb-service:22277 > - dn_rpc_address=iotdb-service > - dn_internal_address=iotdb-service > - dn_target_config_node_list=iotdb-service:22277 > volumes: > - ./data:/iotdb/data > - ./logs:/iotdb/logs > networks: > iotdb: > ipv4_address: 172.18.0.6 > networks: > iotdb: > external: true {code} > What is this for? > > 5. Website dockercompose > {code:java} > version: "3" > services: > iotdb-confignode: > image: apache/iotdb:1.0.0-confignode > container_name: iotdb-confignode > ports: > - "22277:22277" > - "22278:22278" > environment: > - cn_internal_address=iotdb-2 > - cn_target_config_node_list=iotdb-1:22277 > - schema_replication_factor=3 > - > schema_region_consensu
[jira] [Created] (IOTDB-5234) [DOC] Add schema memory allocation upgrading guide
Yukun Zhou created IOTDB-5234: - Summary: [DOC] Add schema memory allocation upgrading guide Key: IOTDB-5234 URL: https://issues.apache.org/jira/browse/IOTDB-5234 Project: Apache IoTDB Issue Type: Improvement Reporter: Yukun Zhou Assignee: Yukun Zhou Fix For: master branch, 1.0.1 The schema memory allocation of 1.0 is different from that of 0.13x, and users should be reminded of this difference to avoid upgrade failure. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5119) [M4]There is an exception in the M4 function query
[ https://issues.apache.org/jira/browse/IOTDB-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649132#comment-17649132 ] xiaozhihong commented on IOTDB-5119: Master branch commit 171b229695eaba309912e5caee547c10d75b13dc !image-2022-12-19-11-41-51-631.png! > [M4]There is an exception in the M4 function query > -- > > Key: IOTDB-5119 > URL: https://issues.apache.org/jira/browse/IOTDB-5119 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query, mpp-cluster >Affects Versions: master branch, 1.0.0 >Reporter: xiaozhihong >Assignee: Lei Rui >Priority: Major > Labels: pull-request-available > Attachments: image-2022-12-05-17-15-28-373.png, > image-2022-12-19-11-41-51-631.png > > > In V1.0, Started 3C3D. > Entered CLI, executed M4 query and reported a exception : > {code:java} > IoTDB> select temperature from root.ln.wf01.wt01; > +-+-+ > | Time|root.ln.wf01.wt01.temperature| > +-+-+ > |2017-11-05T10:20:00.000+08:00| 25.57756| > |2017-11-05T10:21:00.000+08:00| 23.97946| > |2017-11-05T10:22:00.000+08:00| 22.720444| > +-+-+ > Total line number = 3 > It costs 0.007s > IoTDB> select > M4(temperature,'timeInterval'='1000','displayWindowBegin'='1','displayWindowEnd'='100') > from root.ln.wf01.wt01; > Msg: 301: Error occurred during executing UDTF#transform(RowWindow, > PointCollector): > java.lang.IndexOutOfBoundsException: Size is 0{code} > The log is: > !image-2022-12-05-17-15-28-373.png|width=542,height=225! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5235) [SchemaFile] support props
yanze chen created IOTDB-5235: - Summary: [SchemaFile] support props Key: IOTDB-5235 URL: https://issues.apache.org/jira/browse/IOTDB-5235 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yanze chen SchemaFile need to support props. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5034) [ratis] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:1209 - [ChangeRegionLeader] Failed to change the leader of RegionGroup: SchemaRegion[8]
[ https://issues.apache.org/jira/browse/IOTDB-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649172#comment-17649172 ] 刘珍 commented on IOTDB-5034: --- master_1216_d426f7a ,验证通过,数据count验证通过。 > [ratis] ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:1209 - > [ChangeRegionLeader] Failed to change the leader of RegionGroup: > SchemaRegion[8] > --- > > Key: IOTDB-5034 > URL: https://issues.apache.org/jira/browse/IOTDB-5034 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Song Ziyang >Priority: Minor > Labels: pull-request-available > Attachments: iotdb_4851.conf > > > 测试版本:1124_cd839a4 > 在机器上的路径:/data/liuzhen_test/master_1123_32e2f98 (1124_cd839a4的lib) > 1. 启动1副本3C5D集群 > 2.写入数据,完成(配置见附件) > 3.缩容ip76 datanode,最终缩容成功,但是ip62有如下报错: > 2022-11-24 11:24:39,955 [pool-69-IoTDB-DataNodeInternalRPC-Processor-12] > ERROR o.a.i.c.r.RatisConsensus:676 - > org.apache.iotdb.consensus.ratis.RatisConsensus@6c19f01a request failed with > exception {} > org.apache.iotdb.consensus.exception.RatisRequestFailedException: Ratis > request failed > at > org.apache.iotdb.consensus.ratis.RatisConsensus.transferLeader(RatisConsensus.java:545) > at > org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.transferLeader(DataNodeInternalRPCServiceImpl.java:1201) > at > org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.changeRegionLeader(DataNodeInternalRPCServiceImpl.java:1192) > at > org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3932) > at > org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$changeRegionLeader.getResult(IDataNodeRPCService.java:3912) > 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.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.apache.ratis.protocol.exceptions.GroupMismatchException: 6: > group-00020008 not found. > at > org.apache.ratis.server.impl.RaftServerProxy$ImplMap.get(RaftServerProxy.java:150) > at > org.apache.ratis.server.impl.RaftServerProxy.getImplFuture(RaftServerProxy.java:351) > at > org.apache.ratis.server.impl.RaftServerProxy.setConfigurationAsync(RaftServerProxy.java:606) > at > org.apache.ratis.grpc.server.GrpcAdminProtocolService.lambda$setConfiguration$3(GrpcAdminProtocolService.java:70) > at org.apache.ratis.grpc.GrpcUtil.asyncCall(GrpcUtil.java:164) > at > org.apache.ratis.grpc.server.GrpcAdminProtocolService.setConfiguration(GrpcAdminProtocolService.java:70) > at > org.apache.ratis.proto.grpc.AdminProtocolServiceGrpc$MethodHandlers.invoke(AdminProtocolServiceGrpc.java:643) > at > org.apache.ratis.thirdparty.io.grpc.stub.ServerCalls$UnaryServerCallHandler$UnaryServerCallListener.onHalfClose(ServerCalls.java:182) > at > org.apache.ratis.thirdparty.io.grpc.PartialForwardingServerCallListener.onHalfClose(PartialForwardingServerCallListener.java:35) > at > org.apache.ratis.thirdparty.io.grpc.ForwardingServerCallListener.onHalfClose(ForwardingServerCallListener.java:23) > at > org.apache.ratis.thirdparty.io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.halfClosed(ServerCallImpl.java:354) > at > org.apache.ratis.thirdparty.io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1HalfClosed.runInContext(ServerImpl.java:866) > at > org.apache.ratis.thirdparty.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) > at > org.apache.ratis.thirdparty.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.lang.Thread.run(Thread.java:834) > 2022-11-24 11:24:39,956 [pool-69-IoTDB-DataNodeInternalRPC-Processor-12] > ERROR o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:1209 - > [ChangeRegionLeader] Failed to change the leader of RegionGroup: > SchemaRegion[8] > org.apache.iotdb.consensus.exception.RatisRequestFailedException: R
[jira] [Assigned] (IOTDB-5236) DeleteData Python API cannot work
[ https://issues.apache.org/jira/browse/IOTDB-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-5236: - Assignee: Haonan Hou > DeleteData Python API cannot work > - > > Key: IOTDB-5236 > URL: https://issues.apache.org/jira/browse/IOTDB-5236 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.13.3, 1.0.0 >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > > self = > paths_list = ['root.sg2.d1.s1', 'root.sg2.d1.s2', 'root.sg2.d1.s3'] > timestamp = 1 > def delete_data(self, paths_list, timestamp): > """ > delete all data <= time in multiple time series > :param paths_list: time series list that the data in. > :param timestamp: data with time stamp less than or equal to time > will be deleted. > """ > request = TSDeleteDataReq(self.__session_id, paths_list, timestamp) > try: > > status = self.__client.deleteData(request) > ..\..\iotdb-sdk-test\venv\lib\site-packages\iotdb\Session.py:350: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > self = > req = TSDeleteDataReq(sessionId=11, paths=['root.sg2.d1.s1', > 'root.sg2.d1.s2', 'root.sg2.d1.s3'], startTime=1, endTime=None) > def deleteData(self, req): > """ > Parameters: > - req > > """ > self.send_deleteData(req) > > return self.recv_deleteData() > ..\..\iotdb-sdk-test\venv\lib\site-packages\iotdb\thrift\rpc\TSIService.py:1549: > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ > self = > def recv_deleteData(self): > iprot = self._iprot > (fname, mtype, rseqid) = iprot.readMessageBegin() > if mtype == TMessageType.EXCEPTION: > x = TApplicationException() > x.read(iprot) > iprot.readMessageEnd() > > raise x > E thrift.Thrift.TApplicationException: Required field 'endTime' was > not found in serialized data! Struct: > org.apache.iotdb.service.rpc.thrift.TSDeleteDataReq$TSDeleteDataReqStandardScheme@75987fe6 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5236) DeleteData Python API cannot work
Haonan Hou created IOTDB-5236: - Summary: DeleteData Python API cannot work Key: IOTDB-5236 URL: https://issues.apache.org/jira/browse/IOTDB-5236 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.13.3, 1.0.0 Reporter: Haonan Hou self = paths_list = ['root.sg2.d1.s1', 'root.sg2.d1.s2', 'root.sg2.d1.s3'] timestamp = 1 def delete_data(self, paths_list, timestamp): """ delete all data <= time in multiple time series :param paths_list: time series list that the data in. :param timestamp: data with time stamp less than or equal to time will be deleted. """ request = TSDeleteDataReq(self.__session_id, paths_list, timestamp) try: > status = self.__client.deleteData(request) ..\..\iotdb-sdk-test\venv\lib\site-packages\iotdb\Session.py:350: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = req = TSDeleteDataReq(sessionId=11, paths=['root.sg2.d1.s1', 'root.sg2.d1.s2', 'root.sg2.d1.s3'], startTime=1, endTime=None) def deleteData(self, req): """ Parameters: - req """ self.send_deleteData(req) > return self.recv_deleteData() ..\..\iotdb-sdk-test\venv\lib\site-packages\iotdb\thrift\rpc\TSIService.py:1549: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = def recv_deleteData(self): iprot = self._iprot (fname, mtype, rseqid) = iprot.readMessageBegin() if mtype == TMessageType.EXCEPTION: x = TApplicationException() x.read(iprot) iprot.readMessageEnd() > raise x E thrift.Thrift.TApplicationException: Required field 'endTime' was not found in serialized data! Struct: org.apache.iotdb.service.rpc.thrift.TSDeleteDataReq$TSDeleteDataReqStandardScheme@75987fe6 -- This message was sent by Atlassian Jira (v8.20.10#820010)