[jira] [Created] (IOTDB-4729) Column display name is different from SQL
Eric Pai created IOTDB-4729: --- Summary: Column display name is different from SQL Key: IOTDB-4729 URL: https://issues.apache.org/jira/browse/IOTDB-4729 Project: Apache IoTDB Issue Type: Bug Components: Core/Query Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch Attachments: image-2022-10-24-12-19-19-926.png, image-2022-10-24-12-19-55-601.png !image-2022-10-24-12-19-19-926.png! !image-2022-10-24-12-19-55-601.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4728) Unify APIs in session and sessionPool
[ https://issues.apache.org/jira/browse/IOTDB-4728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4728: - Assignee: 马子坤 > Unify APIs in session and sessionPool > - > > Key: IOTDB-4728 > URL: https://issues.apache.org/jira/browse/IOTDB-4728 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Haonan Hou >Assignee: 马子坤 >Priority: Major > > Currently, many APIs in session are not in sessionPool. We need to check and > add them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4728) Unify APIs in session and sessionPool
Haonan Hou created IOTDB-4728: - Summary: Unify APIs in session and sessionPool Key: IOTDB-4728 URL: https://issues.apache.org/jira/browse/IOTDB-4728 Project: Apache IoTDB Issue Type: New Feature Reporter: Haonan Hou Currently, many APIs in session are not in sessionPool. We need to check them and add them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4726) show cluster return with msg: 500 null
[ https://issues.apache.org/jira/browse/IOTDB-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4726: - Assignee: Gaofei Cao > show cluster return with msg: 500 null > -- > > Key: IOTDB-4726 > URL: https://issues.apache.org/jira/browse/IOTDB-4726 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: changxue >Assignee: Gaofei Cao >Priority: Minor > Attachments: image-2022-10-24-11-13-30-723.png, showCluster-logs.txt > > > show cluster return with msg: 500 null > > reproduction: > # start 3C3D cluster successfully > # execute stop-confignode.sh and stop-datanode.sh on the other 2 nodes(not > the leader) > # start-cli.sh -h > # show cluster > > !image-2022-10-24-11-13-30-723.png! > > logs see attachment > > 说明： > 一般来讲，3节点集群，挂掉2个节点就是不可用的。 > 所以这个情况并非不可接受，但是希望将错误提前，比如：在连接时就拒绝连接。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4727) Ratis request failed ： Cannot cast java.lang.NullPointerException to java.io.IOException
刘珍 created IOTDB-4727:
-
Summary: Ratis request failed ： Cannot cast
java.lang.NullPointerException to java.io.IOException
Key: IOTDB-4727
URL: https://issues.apache.org/jira/browse/IOTDB-4727
Project: Apache IoTDB
Issue Type: Bug
Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Song Ziyang
Attachments: more_ts.conf
master_1023_2fea011
schema region : ratis
data region : multiLeader
3rep , 3C3D
ip66 /data/liuzhen_test/master_1023_2fea011/logs datanode :
2022-10-24 11:21:39,969 [pool-22-IoTDB-DataNodeInternalRPC-Processor-8] ERROR
o.a.i.d.m.e.e.RegionWriteExecutor$WritePlanNodeExecutionVisitor:131 -
{color:#DE350B}*Something wrong happened while calling consensus layer's write
API.*{color}
org.apache.iotdb.consensus.exception.RatisRequestFailedException: Ratis request
failed
at
org.apache.iotdb.consensus.ratis.RatisConsensus.write(RatisConsensus.java:262)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.executePlanNodeInConsensusLayer(RegionWriteExecutor.java:146)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitPlan(RegionWriteExecutor.java:123)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitPlan(RegionWriteExecutor.java:113)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.PlanVisitor.visitCreateMultiTimeSeries(PlanVisitor.java:214)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:368)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor$WritePlanNodeExecutionVisitor.visitCreateMultiTimeSeries(RegionWriteExecutor.java:113)
at
org.apache.iotdb.db.mpp.plan.planner.plan.node.metedata.write.CreateMultiTimeSeriesNode.accept(CreateMultiTimeSeriesNode.java:141)
at
org.apache.iotdb.db.mpp.execution.executor.RegionWriteExecutor.execute(RegionWriteExecutor.java:79)
at
org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.sendPlanNode(DataNodeInternalRPCServiceImpl.java:227)
at
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$sendPlanNode.getResult(IDataNodeRPCService.java:3221)
at
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$sendPlanNode.getResult(IDataNodeRPCService.java:3201)
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.RaftRetryFailureException:
Failed RaftClientRequest:client-B007979C3BB9->5@group-00020007, cid=16,
seq=0, RW, org.apache.iotdb.consensus.ratis.RequestMessage@61a2e19e for 2
attempts with
org.apache.iotdb.consensus.ratis.RatisClient$RatisRetryPolicy@25d595d4
at
org.apache.ratis.client.impl.RaftClientImpl.noMoreRetries(RaftClientImpl.java:307)
at
org.apache.ratis.client.impl.BlockingImpl.sendRequestWithRetry(BlockingImpl.java:119)
at org.apache.ratis.client.impl.BlockingImpl.send(BlockingImpl.java:85)
at org.apache.ratis.client.impl.BlockingImpl.send(BlockingImpl.java:59)
at
org.apache.iotdb.consensus.ratis.RatisConsensus.lambda$writeRemotelyWithRetry$2(RatisConsensus.java:198)
at
org.apache.iotdb.consensus.ratis.RatisConsensus.writeWithRetry(RatisConsensus.java:176)
at
org.apache.iotdb.consensus.ratis.RatisConsensus.writeRemotelyWithRetry(RatisConsensus.java:198)
at
org.apache.iotdb.consensus.ratis.RatisConsensus.write(RatisConsensus.java:256)
... 17 common frames omitted
Caused by: java.io.IOException: java.lang.NullPointerException
at org.apache.ratis.util.IOUtils.asIOException(IOUtils.java:56)
at org.apache.ratis.grpc.GrpcUtil.tryUnwrapException(GrpcUtil.java:121)
at org.apache.ratis.grpc.GrpcUtil.unwrapException(GrpcUtil.java:91)
at org.apache.ratis.grpc.GrpcUtil.unwrapIOException(GrpcUtil.java:152)
at
org.apache.ratis.grpc.client.GrpcClientRpc$1.onError(GrpcClientRpc.java:156)
at
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:487)
at
org.apache.ratis.thirdparty.io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39)
at
[jira] [Created] (IOTDB-4726) show cluster return with msg: 500 null
changxue created IOTDB-4726: --- Summary: show cluster return with msg: 500 null Key: IOTDB-4726 URL: https://issues.apache.org/jira/browse/IOTDB-4726 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: changxue Attachments: image-2022-10-24-11-13-30-723.png, showCluster-logs.txt show cluster return with msg: 500 null reproduction: # start 3C3D cluster successfully # execute stop-confignode.sh and stop-datanode.sh on the other 2 nodes(not the leader) # start-cli.sh -h # show cluster !image-2022-10-24-11-13-30-723.png! logs see attachment 说明： 一般来讲，3节点集群，挂掉2个节点就是不可用的。 所以这个情况并非不可接受，但是希望将错误提前，比如：在连接时就拒绝连接。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4725) Support loading data in order by each timeseries
Jialin Qiao created IOTDB-4725: -- Summary: Support loading data in order by each timeseries Key: IOTDB-4725 URL: https://issues.apache.org/jira/browse/IOTDB-4725 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao In some cases, users would like to load some history data from other database into IoTDB. The write mode is insert timeseries1 from t_min to t_max insert timeseries2 from t_min to t_max insert timeseries3 from t_min to t_max If we use the seq/unseq check in device granularity, there may produce many unseq data. In this case, we could use an empty IoTDB for historical data loading. Add a parameter chronological_in_series, for each time point, we put it in sequence space without unseq check, but check in TVList if it is in order. When a TVList is newly created, we compare its last time in last_cache. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4724) [UDF] Refactor UDFExecutableManager for new UDF management
liaolanyu created IOTDB-4724: Summary: [UDF] Refactor UDFExecutableManager for new UDF management Key: IOTDB-4724 URL: https://issues.apache.org/jira/browse/IOTDB-4724 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu UDFExecutableManager need not to be an IService and should not take the responsibility of taking snapshot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4679) [0.14][cluster] Unable to connect to iotdb in private-network using port-mapping
[ https://issues.apache.org/jira/browse/IOTDB-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622920#comment-17622920 ] Jialin Qiao commented on IOTDB-4679: 1. remove the logic of: replace rpc_address by internal_address 2. add doc for rpc_address parameter：Client(Session) will connect to this address, or try to connect to this address when enableRedirection, need to ensure this is accessible by client 3. Add a constructor for Session to add enableRedirection parameter, do not change existing constructor 4. Disable redirection in Cli 5. If Session meets a redirection address of 0.0.0.0, skip it 6. If Session redirection failed for 5 times, do not try forever > [0.14][cluster] Unable to connect to iotdb in private-network using > port-mapping > > > Key: IOTDB-4679 > URL: https://issues.apache.org/jira/browse/IOTDB-4679 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.14.0-preview2 >Reporter: ZhangZhengming >Assignee: Quan Siyi >Priority: Major > Labels: pull-request-available > Fix For: 0.14.0 > > Attachments: image-2022-10-18-16-17-43-132.png, > image-2022-10-18-16-18-32-594.png, image-2022-10-18-16-22-14-107.png, > image-2022-10-18-16-58-54-509.png, image-2022-10-18-16-59-48-604.png, > image-2022-10-18-17-09-48-843.png, image-2022-10-18-17-23-09-941.png, > image-2022-10-18-17-27-20-958.png, image-2022-10-18-17-32-01-496.png, > image-2022-10-18-17-33-12-224.png > > > I want to use port-mapping to expose rpc-port to the public network > I set rpc_address=0.0.0.0，internal_address=172.20.31.67(private_ip) > start iotdb-datanode.sh，the rpc_port listen to 172.20.31.67，instead of > 0.0.0.0，and this port cannot be connected by iotdb-client on the public > network > !image-2022-10-18-17-09-48-843.png|width=636,height=195! > I set rpc_address=111.xxx.xx.xxx (public-ip), The error is reported as > follows > !image-2022-10-18-17-27-20-958.png|width=1367,height=610! > What should I do? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4722) modify Show UDF process on ConfigNode
[ https://issues.apache.org/jira/browse/IOTDB-4722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-4722: -- Assignee: 李伟豪 > modify Show UDF process on ConfigNode > -- > > Key: IOTDB-4722 > URL: https://issues.apache.org/jira/browse/IOTDB-4722 > Project: Apache IoTDB > Issue Type: Task > Components: mpp-cluster >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > > show UDFs on ConfigNode -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4721) modify Create UDF process on ConfigNode
[ https://issues.apache.org/jira/browse/IOTDB-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-4721: -- Assignee: 李伟豪 > modify Create UDF process on ConfigNode > --- > > Key: IOTDB-4721 > URL: https://issues.apache.org/jira/browse/IOTDB-4721 > Project: Apache IoTDB > Issue Type: Task > Components: mpp-cluster >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > > 1.modify Jar transmission; > 2.use Procedure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4723) modify Drop UDF process on ConfigNode
李伟豪 created IOTDB-4723: -- Summary: modify Drop UDF process on ConfigNode Key: IOTDB-4723 URL: https://issues.apache.org/jira/browse/IOTDB-4723 Project: Apache IoTDB Issue Type: Task Components: mpp-cluster Reporter: 李伟豪 use Procedure -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4720) Improve UDF in MPP mode
Yuan Tian created IOTDB-4720: Summary: Improve UDF in MPP mode Key: IOTDB-4720 URL: https://issues.apache.org/jira/browse/IOTDB-4720 Project: Apache IoTDB Issue Type: Epic Reporter: Yuan Tian Assignee: liaolanyu Currently, users need to put udf into each node and udf management does not take restart cases into account. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4719) [SchemaFile] Adaptation for cluster delete timeseries
yanze chen created IOTDB-4719: - Summary: [SchemaFile] Adaptation for cluster delete timeseries Key: IOTDB-4719 URL: https://issues.apache.org/jira/browse/IOTDB-4719 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yanze chen Support 3 interface in SchemaRegionSchemaFileImpl: # constructSchemaBlackList # rollbackSchemaBlackList # deleteTimeseriesInBlackList -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] dependabot[bot] opened a new pull request, #54: Bump github.com/stretchr/testify from 1.8.0 to 1.8.1
dependabot[bot] opened a new pull request, #54: URL: https://github.com/apache/iotdb-client-go/pull/54 Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.8.0 to 1.8.1. Commits https://github.com/stretchr/testify/commit/b747d7c5f853d017ddbc5e623d026d7fc2770a58;>b747d7c Bump github.com/stretchr/objx from 0.4.0 to 0.5.0 (https://github-redirect.dependabot.com/stretchr/testify/issues/1283;>#1283) See full diff in https://github.com/stretchr/testify/compare/v1.8.0...v1.8.1;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- 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] [Commented] (IOTDB-4707) [setStorageGroup]Lack of the support for internationalization
[
https://issues.apache.org/jira/browse/IOTDB-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622902#comment-17622902
]
changxue commented on IOTDB-4707:
-
I ran test cases with 3C3D cluster environment again, and this issue exists
too.
> [setStorageGroup]Lack of the support for internationalization
> -
>
> Key: IOTDB-4707
> URL: https://issues.apache.org/jira/browse/IOTDB-4707
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Schema Manager
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: changxue
>Assignee: liaolanyu
>Priority: Minor
>
> Lack of the support for internationalization
> 在创建storage group 时缺少对国际化的系统支持
> tests:
> root.quote1.`française`
> root.quote2.`اللغة العربية`
> root.quote3.`Español`
> root.quote5.`Русский`
> root.quote6.`한국어`
> Create storage group failed when using the path upstairs, but it succeeded
> with Japanese and Chinese.
> {code:java}
> org.apache.iotdb.rpc.StatementExecutionException: 315: The storage group name
> can only be characters, numbers and underscores. root.quote2.`اللغة العربية`
> is not a legal path
> {code}
>
> environment:
> 3C3D cluster distribution
> master branch and the newest source code of Oct.21, 2022
>
> ps:
> # 如果想要支持国际化，那么文档中反引号的说明也应该有体现。
> # 在创建timeseries时，类似的testcase 都创建成功。
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4718) Update user guide of SELECT INTO statement
Minghui Liu created IOTDB-4718: -- Summary: Update user guide of SELECT INTO statement Key: IOTDB-4718 URL: https://issues.apache.org/jira/browse/IOTDB-4718 Project: Apache IoTDB Issue Type: Task Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4717) [UDF] Refactor UDFRegistrationService for new Cluster
liaolanyu created IOTDB-4717: Summary: [UDF] Refactor UDFRegistrationService for new Cluster Key: IOTDB-4717 URL: https://issues.apache.org/jira/browse/IOTDB-4717 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu Currently, in UDFRegistrationService, recovery log of oldStandalone version is kept and we should remove it. Also, this service does not need to be an IService. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4716) [Metric] Fix the statistics of disk size in linux system in 0.13
[ https://issues.apache.org/jira/browse/IOTDB-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17622738#comment-17622738 ] Zhijia Cao commented on IOTDB-4716: --- The method for calculating the total number of disks on the linux server is incomplete. You should calculate the size of all disk mount points except the root directory (/) > [Metric] Fix the statistics of disk size in linux system in 0.13 > > > Key: IOTDB-4716 > URL: https://issues.apache.org/jira/browse/IOTDB-4716 > Project: Apache IoTDB > Issue Type: Bug >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 2h > Remaining Estimate: 2h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4716) [Metric] Fix the statistics of disk size in linux system in 0.13
张洪胤 created IOTDB-4716: -- Summary: [Metric] Fix the statistics of disk size in linux system in 0.13 Key: IOTDB-4716 URL: https://issues.apache.org/jira/browse/IOTDB-4716 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
