[jira] [Created] (IOTDB-6261) Add leader cache function in pipe's SyncConnector
Xuan Ronaldo created IOTDB-6261: --- Summary: Add leader cache function in pipe's SyncConnector Key: IOTDB-6261 URL: https://issues.apache.org/jira/browse/IOTDB-6261 Project: Apache IoTDB Issue Type: Improvement Components: Core/Server Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6248) The connection will close when webSocketServer doesn't response in Flink-CDC-Connector.
Xuan Ronaldo created IOTDB-6248: --- Summary: The connection will close when webSocketServer doesn't response in Flink-CDC-Connector. Key: IOTDB-6248 URL: https://issues.apache.org/jira/browse/IOTDB-6248 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Flink Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6189) Fix bugs for csv-tools (The output is incorrect when the import fails. The csv file with bom header can not be imported. The last line can not be imported )
Xuan Ronaldo created IOTDB-6189: --- Summary: Fix bugs for csv-tools (The output is incorrect when the import fails. The csv file with bom header can not be imported. The last line can not be imported ) Key: IOTDB-6189 URL: https://issues.apache.org/jira/browse/IOTDB-6189 Project: Apache IoTDB Issue Type: Bug Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6163) fix bugs of flink-sql-iotdb-connector for rc3
Xuan Ronaldo created IOTDB-6163: --- Summary: fix bugs of flink-sql-iotdb-connector for rc3 Key: IOTDB-6163 URL: https://issues.apache.org/jira/browse/IOTDB-6163 Project: Apache IoTDB Issue Type: Bug Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6158) add samples and ITs for Flink-sql-connector
Xuan Ronaldo created IOTDB-6158: --- Summary: add samples and ITs for Flink-sql-connector Key: IOTDB-6158 URL: https://issues.apache.org/jira/browse/IOTDB-6158 Project: Apache IoTDB Issue Type: Bug Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6155) fix bugs of flink-sql-iotdb-connector for rc2
Xuan Ronaldo created IOTDB-6155: --- Summary: fix bugs of flink-sql-iotdb-connector for rc2 Key: IOTDB-6155 URL: https://issues.apache.org/jira/browse/IOTDB-6155 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Flink Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6128) supporting multiple device operation in Flink-sql-iotdb-connector
[ https://issues.apache.org/jira/browse/IOTDB-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-6128: --- Component/s: Connectors/Flink Fix Version/s: master branch 1.2.2 Assignee: Xuan Ronaldo Summary: supporting multiple device operation in Flink-sql-iotdb-connector (was: supporting mul) > supporting multiple device operation in Flink-sql-iotdb-connector > - > > Key: IOTDB-6128 > URL: https://issues.apache.org/jira/browse/IOTDB-6128 > Project: Apache IoTDB > Issue Type: New Feature > Components: Connectors/Flink >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: master branch, 1.2.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6128) supporting mul
Xuan Ronaldo created IOTDB-6128: --- Summary: supporting mul Key: IOTDB-6128 URL: https://issues.apache.org/jira/browse/IOTDB-6128 Project: Apache IoTDB Issue Type: New Feature Reporter: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6080) Add batch mode in pipe-connector
Xuan Ronaldo created IOTDB-6080: --- Summary: Add batch mode in pipe-connector Key: IOTDB-6080 URL: https://issues.apache.org/jira/browse/IOTDB-6080 Project: Apache IoTDB Issue Type: New Feature Components: Core/Engine Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6040) removing the module `subscription-api`
Xuan Ronaldo created IOTDB-6040: --- Summary: removing the module `subscription-api` Key: IOTDB-6040 URL: https://issues.apache.org/jira/browse/IOTDB-6040 Project: Apache IoTDB Issue Type: Task Reporter: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6038) fixing the problem about the authorization of mqtt
Xuan Ronaldo created IOTDB-6038: --- Summary: fixing the problem about the authorization of mqtt Key: IOTDB-6038 URL: https://issues.apache.org/jira/browse/IOTDB-6038 Project: Apache IoTDB Issue Type: Bug Reporter: Xuan Ronaldo Assignee: Hongyin Zhang 命令行修改root账号的密码，重启iotdb后，mqtt的账号密码还是root/root，不因数据库密码的改变而改变，而启用了reset服务后，http接口的密码是随着root账号的密码修改而修改的，刚刚出现的mqtt接口失效的问题，可能与修改root账号密码有关，因为我修改了root密码后，无法通过mqtt写入数据库，但是，iotdb的mqtt此时是可以通过root/root连接的。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6029) Implement flink-sql-iotdb-connector
Xuan Ronaldo created IOTDB-6029: --- Summary: Implement flink-sql-iotdb-connector Key: IOTDB-6029 URL: https://issues.apache.org/jira/browse/IOTDB-6029 Project: Apache IoTDB Issue Type: New Feature Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6004) throwing error `301: queue has been destroyed` when query is longer than 60s in ExportCSV tool
[ https://issues.apache.org/jira/browse/IOTDB-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-6004: --- Assignee: Xuan Ronaldo > throwing error `301: queue has been destroyed` when query is longer than 60s > in ExportCSV tool > -- > > Key: IOTDB-6004 > URL: https://issues.apache.org/jira/browse/IOTDB-6004 > Project: Apache IoTDB > Issue Type: Task > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: master branch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6004) throwing error `301: queue has been destroyed` when query is longer than 60s in ExportCSV tool
[ https://issues.apache.org/jira/browse/IOTDB-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-6004: --- Assignee: (was: Xuan Ronaldo) > throwing error `301: queue has been destroyed` when query is longer than 60s > in ExportCSV tool > -- > > Key: IOTDB-6004 > URL: https://issues.apache.org/jira/browse/IOTDB-6004 > Project: Apache IoTDB > Issue Type: Task > Components: Client/CLI >Reporter: Xuan Ronaldo >Priority: Major > Fix For: master branch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6004) throwing error `301: queue has been destroyed` when query is longer than 60s in ExportCSV tool
Xuan Ronaldo created IOTDB-6004: --- Summary: throwing error `301: queue has been destroyed` when query is longer than 60s in ExportCSV tool Key: IOTDB-6004 URL: https://issues.apache.org/jira/browse/IOTDB-6004 Project: Apache IoTDB Issue Type: Task Components: Client/CLI Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: master branch -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5990) Pipe unexpectedly stop when an aligned device is piped
[
https://issues.apache.org/jira/browse/IOTDB-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Ronaldo reassigned IOTDB-5990:
---
Assignee: (was: Xuan Ronaldo)
> Pipe unexpectedly stop when an aligned device is piped
> --
>
> Key: IOTDB-5990
> URL: https://issues.apache.org/jira/browse/IOTDB-5990
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Others
>Reporter: 马子坤
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2023-06-12-18-43-59-399.png,
> image-2023-06-12-18-48-15-389.png, receiver_logs.zip, sender_logs.zip
>
>
> 接收端未创建device，用pipe同步aligned device会导致pipe自动停止
> 日志见附件
> 复现步骤：
> insert into root.sg1.d1(time, at1) aligned values (now(), 1);
> create pipe p1 with collector ('collector.pattern'='root.sg1.d1') with
> connector
> ('connector'='iotdb_thrift_connector','connector.ip'='127.0.0.1','connector.port'='6668');
> start pipe p1;
> create pipe p2 with connector
> ('connector'='iotdb_thrift_connector','connector.ip'='127.0.0.1','connector.port'='6668');
> start pipe p2;
> insert into root.sg1.d2(time, at1) aligned values (now(), 2);
> show pipes;
> // 接收端查不到d2这个device，不断show
> pipes，会发现两个pipe均变成STOPPED。此后手动start两个pipe，也不同步d1的实时数据了
> !image-2023-06-12-18-48-15-389.png|width=147,height=106!
> !image-2023-06-12-18-43-59-399.png|width=759,height=389!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5990) Pipe unexpectedly stop when an aligned device is piped
[
https://issues.apache.org/jira/browse/IOTDB-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Ronaldo reassigned IOTDB-5990:
---
Assignee: Xuan Ronaldo
> Pipe unexpectedly stop when an aligned device is piped
> --
>
> Key: IOTDB-5990
> URL: https://issues.apache.org/jira/browse/IOTDB-5990
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Others
>Reporter: 马子坤
>Assignee: Xuan Ronaldo
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2023-06-12-18-43-59-399.png,
> image-2023-06-12-18-48-15-389.png, receiver_logs.zip, sender_logs.zip
>
>
> 接收端未创建device，用pipe同步aligned device会导致pipe自动停止
> 日志见附件
> 复现步骤：
> insert into root.sg1.d1(time, at1) aligned values (now(), 1);
> create pipe p1 with collector ('collector.pattern'='root.sg1.d1') with
> connector
> ('connector'='iotdb_thrift_connector','connector.ip'='127.0.0.1','connector.port'='6668');
> start pipe p1;
> create pipe p2 with connector
> ('connector'='iotdb_thrift_connector','connector.ip'='127.0.0.1','connector.port'='6668');
> start pipe p2;
> insert into root.sg1.d2(time, at1) aligned values (now(), 2);
> show pipes;
> // 接收端查不到d2这个device，不断show
> pipes，会发现两个pipe均变成STOPPED。此后手动start两个pipe，也不同步d1的实时数据了
> !image-2023-06-12-18-48-15-389.png|width=147,height=106!
> !image-2023-06-12-18-43-59-399.png|width=759,height=389!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5913) A query error occurs after a new user is authorized
Xuan Ronaldo created IOTDB-5913: --- Summary: A query error occurs after a new user is authorized Key: IOTDB-5913 URL: https://issues.apache.org/jira/browse/IOTDB-5913 Project: Apache IoTDB Issue Type: Task Reporter: Xuan Ronaldo command: `grant user XYZSGDB privileges READ TIMESERIES on root.sb.0742` query1: `select * from root.sb.0742.ACQUISITION STATUS.5160013` result: `Msg: 602: No permissions for this operation, please add privilege READ TIMESERIES` query2: `select **from root.sb.0742.ACQUISITION STATUS.5160013` result: `normal` query3: `select * from root.sb.0742.ACQUISITION STATUS.5160013.cjfwzt` result: `normal` -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5772) Update spark-iotdb-connnector
Xuan Ronaldo created IOTDB-5772: --- Summary: Update spark-iotdb-connnector Key: IOTDB-5772 URL: https://issues.apache.org/jira/browse/IOTDB-5772 Project: Apache IoTDB Issue Type: Task Components: Connectors/Spark-IoTDB Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: master branch, 0.13.4-SNAPSHOT The spark-iotdb-connector of current version is not useable in Spark with scala2.12. We will release a new version to resolve this problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5759) fix erratum of Spark-IoTDB's doc
[ https://issues.apache.org/jira/browse/IOTDB-5759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-5759: --- Assignee: Xuan Ronaldo > fix erratum of Spark-IoTDB's doc > > > Key: IOTDB-5759 > URL: https://issues.apache.org/jira/browse/IOTDB-5759 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Spark-IoTDB >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > > There are a couple of erratum in Spark-IoTDB's doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5759) fix erratum of Spark-IoTDB's doc
Xuan Ronaldo created IOTDB-5759: --- Summary: fix erratum of Spark-IoTDB's doc Key: IOTDB-5759 URL: https://issues.apache.org/jira/browse/IOTDB-5759 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Spark-IoTDB Reporter: Xuan Ronaldo There are a couple of erratum in Spark-IoTDB's doc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5249) add interface to set datatype when users customize the payload formatter of mqtt
Xuan Ronaldo created IOTDB-5249: --- Summary: add interface to set datatype when users customize the payload formatter of mqtt Key: IOTDB-5249 URL: https://issues.apache.org/jira/browse/IOTDB-5249 Project: Apache IoTDB Issue Type: Improvement Components: Core/Others Reporter: Xuan Ronaldo Assignee: Haonan Hou Fix For: master branch Attachments: image-2022-12-20-15-40-17-574.png Now, there is not interface to set datatype when we customize the payload formatter of mqtt. !image-2022-12-20-15-40-17-574.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5028) Using `show timeseries` to query the schema in import-csv
Xuan Ronaldo created IOTDB-5028: --- Summary: Using `show timeseries` to query the schema in import-csv Key: IOTDB-5028 URL: https://issues.apache.org/jira/browse/IOTDB-5028 Project: Apache IoTDB Issue Type: Improvement Components: Client/CLI Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: master branch The import-csv tool is using `select * from ... limit 1` to query the schema. It will cost a lot of performance. Therefore, we need to use `show timeseries` to query the schema. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4312) header parsing error in ImportCSV
Xuan Ronaldo created IOTDB-4312: --- Summary: header parsing error in ImportCSV Key: IOTDB-4312 URL: https://issues.apache.org/jira/browse/IOTDB-4312 Project: Apache IoTDB Issue Type: Bug Components: CI Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: 0.14.0-SNAPSHOT, 0.13.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4305) fix website building
Xuan Ronaldo created IOTDB-4305: --- Summary: fix website building Key: IOTDB-4305 URL: https://issues.apache.org/jira/browse/IOTDB-4305 Project: Apache IoTDB Issue Type: Bug Components: Website Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Attachments: 81fc776530e4a057a520f93239b3cb2.jpg !81fc776530e4a057a520f93239b3cb2.jpg! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4190) update documents about nifi-iotdb-bundle
Xuan Ronaldo created IOTDB-4190: --- Summary: update documents about nifi-iotdb-bundle Key: IOTDB-4190 URL: https://issues.apache.org/jira/browse/IOTDB-4190 Project: Apache IoTDB Issue Type: New Feature Components: Document Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo update the userguide of nifi-iotdb-bundle -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-2852) the import-csv tool can not import the data to nonaligned device
Xuan Ronaldo created IOTDB-2852: --- Summary: the import-csv tool can not import the data to nonaligned device Key: IOTDB-2852 URL: https://issues.apache.org/jira/browse/IOTDB-2852 Project: Apache IoTDB Issue Type: Bug Components: csv Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2822) the result of query statement filtered by utc time is incorrect
Xuan Ronaldo created IOTDB-2822: --- Summary: the result of query statement filtered by utc time is incorrect Key: IOTDB-2822 URL: https://issues.apache.org/jira/browse/IOTDB-2822 Project: Apache IoTDB Issue Type: Improvement Components: Client/Java Reporter: Xuan Ronaldo Assignee: Alima777 Attachments: image-2022-03-30-15-13-40-704.png, image-2022-03-30-15-15-52-132.png When using session to query data, the result of query statement filtered by utc time is incorrect. However, it was correct by cli. The debug info of cli (timestamps of utc time and time with zone are same): !image-2022-03-30-15-13-40-704.png! The debug info of session: !image-2022-03-30-15-15-52-132.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2785) using HTTP connection pool to optimize the test of influxdb
Xuan Ronaldo created IOTDB-2785: --- Summary: using HTTP connection pool to optimize the test of influxdb Key: IOTDB-2785 URL: https://issues.apache.org/jira/browse/IOTDB-2785 Project: Apache IoTDB Issue Type: Improvement Components: Benchmark Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2644) Should we provide two versions of Spark and Flink connectors？
Xuan Ronaldo created IOTDB-2644: --- Summary: Should we provide two versions of Spark and Flink connectors？ Key: IOTDB-2644 URL: https://issues.apache.org/jira/browse/IOTDB-2644 Project: Apache IoTDB Issue Type: Wish Components: Connectors/Flink, Connectors/Spark-IoTDB Reporter: Xuan Ronaldo There is some problem of compatibility about scala's version. Maybe we can provide Scala_2.11 and Scala_2.12 two versions of Spark and Flink connectors. If someboby use Spark with Scala_2.11, they can import the depency of flink-iotdb-connector_2.11. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2639) the guide of Flink connector need to be improved
Xuan Ronaldo created IOTDB-2639: --- Summary: the guide of Flink connector need to be improved Key: IOTDB-2639 URL: https://issues.apache.org/jira/browse/IOTDB-2639 Project: Apache IoTDB Issue Type: Improvement Components: Connectors/Flink Reporter: Xuan Ronaldo The Flink-connector was compiled by Scala_2.11, it should be mentioned in guide. If somebody import the dependency of flink-connector-kafka, the program will throw an exception. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2604) batch size is invalid in import-csv tool
Xuan Ronaldo created IOTDB-2604: --- Summary: batch size is invalid in import-csv tool Key: IOTDB-2604 URL: https://issues.apache.org/jira/browse/IOTDB-2604 Project: Apache IoTDB Issue Type: Bug Components: Client/CLI Reporter: Xuan Ronaldo Fix For: 0.13.0-SNAPSHOT, 0.12.5-SNAPSHOT Attachments: image-2022-02-24-15-46-12-113.png The const BATCH_SIZE is invalid in import-csv tool. !image-2022-02-24-15-46-12-113.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2604) batch size is invalid in import-csv tool
[ https://issues.apache.org/jira/browse/IOTDB-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-2604: --- Assignee: Xuan Ronaldo > batch size is invalid in import-csv tool > > > Key: IOTDB-2604 > URL: https://issues.apache.org/jira/browse/IOTDB-2604 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: 0.13.0-SNAPSHOT, 0.12.5-SNAPSHOT > > Attachments: image-2022-02-24-15-46-12-113.png > > > The const BATCH_SIZE is invalid in import-csv tool. > !image-2022-02-24-15-46-12-113.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2496) [benchmark] TEMPLATE=false VECTOR=true ，device name contains ".vector"
[ https://issues.apache.org/jira/browse/IOTDB-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-2496: --- Assignee: Xuan Ronaldo > [benchmark] TEMPLATE=false VECTOR=true ，device name contains ".vector" > -- > > Key: IOTDB-2496 > URL: https://issues.apache.org/jira/browse/IOTDB-2496 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 刘珍 >Assignee: Xuan Ronaldo >Priority: Major > > TEMPLATE=false VECTOR=true ，生成的device名称以.vector结尾 > 应该去掉.vector -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-2440) [template] Template with aligned timeseries , the query result is incorrect
[
https://issues.apache.org/jira/browse/IOTDB-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Ronaldo reassigned IOTDB-2440:
---
Assignee: Xuan Ronaldo
> [template] Template with aligned timeseries , the query result is incorrect
> ---
>
> Key: IOTDB-2440
> URL: https://issues.apache.org/jira/browse/IOTDB-2440
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: 0.13.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Xuan Ronaldo
>Priority: Major
> Attachments: image-2022-01-19-16-28-36-603.png
>
>
> 测试用例：
> create schema template t_vector(gps( s_0 BOOLEAN encoding=PLAIN
> compression=SNAPPY,s_1 INT32 encoding=PLAIN compression=SNAPPY,s_2 INT64
> encoding=PLAIN compression=SNAPPY,s_3 FLOAT encoding=PLAIN
> compression=SNAPPY,s_4 DOUBLE encoding=PLAIN compression=SNAPPY,s_5 TEXT
> encoding=PLAIN compression=SNAPPY));
> set schema template t_vector to root.db_vector;
> insert into root.db_vector.dev.gps(time,s_4)aligned values (1,2.34);
> select * from root.db_vector.dev.gps;
> {color:#DE350B}查询结果为空，不正确。{color}
> show timeseries;
> show devices;
> !image-2022-01-19-16-28-36-603.png!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IOTDB-2347) get an error when using aligned interfaces
Xuan Ronaldo created IOTDB-2347: --- Summary: get an error when using aligned interfaces Key: IOTDB-2347 URL: https://issues.apache.org/jira/browse/IOTDB-2347 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager Reporter: Xuan Ronaldo Attachments: image-2022-01-11-12-30-20-963.png, image-2022-01-11-12-30-40-857.png Getting an error when using aligned interfaces, If the measurement length of each records are not same. !image-2022-01-11-12-30-20-963.png! The data like this: !image-2022-01-11-12-30-40-857.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2324) Support align by device query in benchmark
[ https://issues.apache.org/jira/browse/IOTDB-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472423#comment-17472423 ] Xuan Ronaldo commented on IOTDB-2324: - Can I add a parameter `aligned_by_device`? Then we don't need another ten kinds of query. > Support align by device query in benchmark > -- > > Key: IOTDB-2324 > URL: https://issues.apache.org/jira/browse/IOTDB-2324 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: Yuan Tian >Assignee: Xuan Ronaldo >Priority: Minor > Original Estimate: 8h > Remaining Estimate: 8h > > Now, we support ten kinds of query(Q1~Q10) in benchmark, but align by device > query is not included. > You can see the usage of `align by device` in this > [link|[https://iotdb.apache.org/UserGuide/Master/IoTDB-SQL-Language/DML-Data-Manipulation-Language.html#other-resultset-formats].] > > We need to support `align by device` in benchmark, and in fact, each previous > kind of query should have a corresponding align by device version, so we need > to add another ten kinds of query(Q11-Q20). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2333) the todf method of python client throws exception
[ https://issues.apache.org/jira/browse/IOTDB-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471796#comment-17471796 ] Xuan Ronaldo commented on IOTDB-2333: - I have tested in v0.12.2, v0.12.4, v0.13.0 > the todf method of python client throws exception > - > > Key: IOTDB-2333 > URL: https://issues.apache.org/jira/browse/IOTDB-2333 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/Python >Reporter: Xuan Ronaldo >Priority: Major > Attachments: image-2022-01-10-17-30-20-620.png > > > !image-2022-01-10-17-30-20-620.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2333) the todf method of python client throws exception
Xuan Ronaldo created IOTDB-2333: --- Summary: the todf method of python client throws exception Key: IOTDB-2333 URL: https://issues.apache.org/jira/browse/IOTDB-2333 Project: Apache IoTDB Issue Type: Bug Components: Client/Python Reporter: Xuan Ronaldo Attachments: image-2022-01-10-17-30-20-620.png !image-2022-01-10-17-30-20-620.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2330) fix bugs of CSV tools for 0.13
Xuan Ronaldo created IOTDB-2330: --- Summary: fix bugs of CSV tools for 0.13 Key: IOTDB-2330 URL: https://issues.apache.org/jira/browse/IOTDB-2330 Project: Apache IoTDB Issue Type: Bug Components: Client/CLI Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: 0.13.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2197) datatype conversion exception
Xuan Ronaldo created IOTDB-2197: --- Summary: datatype conversion exception Key: IOTDB-2197 URL: https://issues.apache.org/jira/browse/IOTDB-2197 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Spark-IoTDB Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: 0.12.4 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2185) get an exception when parsing the header of CSV
[ https://issues.apache.org/jira/browse/IOTDB-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463535#comment-17463535 ] Xuan Ronaldo commented on IOTDB-2185: - The bug of 0.12 was fixed in [[To rel/0.12][IoTDB-2185] get an exception when parsing the header of CSV by xuanronaldo · Pull Request #4618 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/4618]. > get an exception when parsing the header of CSV > --- > > Key: IOTDB-2185 > URL: https://issues.apache.org/jira/browse/IOTDB-2185 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: 0.13.0, 0.12.2, 0.12.3, 0.12.4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2185) get an exception when parsing the header of CSV
[ https://issues.apache.org/jira/browse/IOTDB-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463534#comment-17463534 ] Xuan Ronaldo commented on IOTDB-2185: - The bug of 0.12 was fixed in [[To rel/0.12][IoTDB-2185] get an exception when parsing the header of CSV by xuanronaldo · Pull Request #4618 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/4618]. > get an exception when parsing the header of CSV > --- > > Key: IOTDB-2185 > URL: https://issues.apache.org/jira/browse/IOTDB-2185 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: 0.13.0, 0.12.2, 0.12.3, 0.12.4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2185) get an exception when parsing the header of CSV
[ https://issues.apache.org/jira/browse/IOTDB-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463533#comment-17463533 ] Xuan Ronaldo commented on IOTDB-2185: - The bug of 0.12 was fixed in [[To rel/0.12][IoTDB-2185] get an exception when parsing the header of CSV by xuanronaldo · Pull Request #4618 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/4618]. > get an exception when parsing the header of CSV > --- > > Key: IOTDB-2185 > URL: https://issues.apache.org/jira/browse/IOTDB-2185 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: 0.13.0, 0.12.2, 0.12.3, 0.12.4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (IOTDB-2185) get an exception when parsing the header of CSV
[ https://issues.apache.org/jira/browse/IOTDB-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463532#comment-17463532 ] Xuan Ronaldo commented on IOTDB-2185: - The bug of 0.13 was fixed in [[IoTDB-2185] get an exception when parsing the header of CSV by xuanronaldo · Pull Request #4620 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/4620]. > get an exception when parsing the header of CSV > --- > > Key: IOTDB-2185 > URL: https://issues.apache.org/jira/browse/IOTDB-2185 > Project: Apache IoTDB > Issue Type: Bug > Components: Client/CLI >Reporter: Xuan Ronaldo >Assignee: Xuan Ronaldo >Priority: Major > Fix For: 0.13.0, 0.12.2, 0.12.3, 0.12.4 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2185) get an exception when parsing the header of CSV
Xuan Ronaldo created IOTDB-2185: --- Summary: get an exception when parsing the header of CSV Key: IOTDB-2185 URL: https://issues.apache.org/jira/browse/IOTDB-2185 Project: Apache IoTDB Issue Type: Bug Components: Client/CLI Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo Fix For: 0.12.4, 0.12.3, 0.12.2 Attachments: image-2021-12-21-15-14-04-392.png !image-2021-12-21-15-14-04-392.png! -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IOTDB-2119) IoTDB CSV export tools add timestamp accuracy setting function
Xuan Ronaldo created IOTDB-2119: --- Summary: IoTDB CSV export tools add timestamp accuracy setting function Key: IOTDB-2119 URL: https://issues.apache.org/jira/browse/IOTDB-2119 Project: Apache IoTDB Issue Type: Improvement Components: Tools/Others Reporter: Xuan Ronaldo Assignee: Xuan Ronaldo -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-1707) About Kafka's write mode support
[ https://issues.apache.org/jira/browse/IOTDB-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1707: --- Assignee: Xuan Ronaldo > About Kafka's write mode support > > > Key: IOTDB-1707 > URL: https://issues.apache.org/jira/browse/IOTDB-1707 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-1708) Benchmark needs to provide support for inserting different devices in a batch
[ https://issues.apache.org/jira/browse/IOTDB-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1708: --- Assignee: Xuan Ronaldo > Benchmark needs to provide support for inserting different devices in a batch > - > > Key: IOTDB-1708 > URL: https://issues.apache.org/jira/browse/IOTDB-1708 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Minor > > insertTablets (multiple devices, multiple rows and the same column) > insertTablet (single device, multiple rows and the same column) > insertRecordsOfOneDevice (single device with multiple rows and different > columns) > insertRecords(Object value) (multiple devices, multiple rows and different > columns) > insertRecords(String value) (multiple devices, multiple rows and different > columns) > insertRecord (one line for a single device) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (IOTDB-1887) In a clean IOTDB, without creating metadata, directly importing data containing null indicates an exception
[ https://issues.apache.org/jira/browse/IOTDB-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1887: --- Assignee: Xuan Ronaldo > In a clean IOTDB, without creating metadata, directly importing data > containing null indicates an exception > --- > > Key: IOTDB-1887 > URL: https://issues.apache.org/jira/browse/IOTDB-1887 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Affects Versions: 0.12.3 >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > > The process is as follows： > Step 1： start a clean Iotdb sever > Step 2: Execute import command > ./import-csv.sh -h 127.0.0.1 -p 6667 -u root -pw root -f > /home/xzh/csv-data/sg.txt > Then will see log: > 15:31:51.210 [main] DEBUG org.apache.iotdb.session.Session - > EndPoint(ip:127.0.0.1, port:6667) execute sql select * from > root.sg.d1,root.sg.d2 limit 1 > -MM-dd'T'HH:mm:ss.SSSX > Line 3: null can't convert to INT32 > Line 3: null can't convert to FLOAT > Line 4: null can't convert to INT32 > Line 4: null can't convert to FLOAT > Line 1: null can't convert to INT64 > Line 1: null can't convert to INT64 > Line 1: null can't convert to INT64 > Line 2: null can't convert to INT64 > Line 2: null can't convert to INT64 > Line 2: null can't convert to INT64 > Line 3: 2.0 can't convert to INT64 > Line 3: null can't convert to INT64 > Line 4: 2.0 can't convert to INT64 > Line 4: true can't convert to INT64 > Import completely! > sg.txt > ``` > Time,root.sg.d1.s1,root.sg.d1.s2,root.sg.d2.s1,root.sg.d2.s2,root.sg.d2.s3 > 2020-08-18T10:22:31.603+08:00,1,2.0,null,null,null > 2020-08-18T10:22:35.631+08:00,1,2.0,null,null,null > 2020-08-18T10:22:41.093+08:00,null,null,1,2.0,null > 2020-08-18T10:22:52.603+08:00,null,null,1,2.0,true > ``` > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1686) Benchmark support opentsdb and kairosdb
[ https://issues.apache.org/jira/browse/IOTDB-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427525#comment-17427525 ] Xuan Ronaldo commented on IOTDB-1686: - The KairosDB was fixed in [fix KairosDB and add sample configuration file. by xuanronaldo · Pull Request #207 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/207]. > Benchmark support opentsdb and kairosdb > --- > > Key: IOTDB-1686 > URL: https://issues.apache.org/jira/browse/IOTDB-1686 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: Hai Liu >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1686) Benchmark support opentsdb and kairosdb
[ https://issues.apache.org/jira/browse/IOTDB-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426926#comment-17426926 ] Xuan Ronaldo commented on IOTDB-1686: - The opentsdb was fixed in [Fix opentsdb and the issue of #201 by xuanronaldo · Pull Request #204 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/204]. > Benchmark support opentsdb and kairosdb > --- > > Key: IOTDB-1686 > URL: https://issues.apache.org/jira/browse/IOTDB-1686 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: Hai Liu >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1788) [Benchmark]There maybe some problem in Q4 in benchmark(opentsdb)
[ https://issues.apache.org/jira/browse/IOTDB-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426925#comment-17426925 ] Xuan Ronaldo commented on IOTDB-1788: - It was fixed in [Fix opentsdb and the issue of #201 by xuanronaldo · Pull Request #204 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/204]. > [Benchmark]There maybe some problem in Q4 in benchmark(opentsdb) > > > Key: IOTDB-1788 > URL: https://issues.apache.org/jira/browse/IOTDB-1788 > Project: Apache IoTDB > Issue Type: Bug > Components: Benchmark >Reporter: 张洪胤 >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 16h > Remaining Estimate: 16h > > The issue: https://github.com/thulab/iotdb-benchmark/issues/201 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1684) Support PI JDBC in Benchmark
[ https://issues.apache.org/jira/browse/IOTDB-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420452#comment-17420452 ] Xuan Ronaldo commented on IOTDB-1684: - [Support JDBC of PI Archive by xuanronaldo · Pull Request #196 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/196] > Support PI JDBC in Benchmark > > > Key: IOTDB-1684 > URL: https://issues.apache.org/jira/browse/IOTDB-1684 > Project: Apache IoTDB > Issue Type: Task > Components: Benchmark >Reporter: Hai Liu >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 12h > Remaining Estimate: 12h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1685) Benchmark support Insert operation in PI
[ https://issues.apache.org/jira/browse/IOTDB-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420453#comment-17420453 ] Xuan Ronaldo commented on IOTDB-1685: - [Support JDBC of PI Archive by xuanronaldo · Pull Request #196 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/196] > Benchmark support Insert operation in PI > - > > Key: IOTDB-1685 > URL: https://issues.apache.org/jira/browse/IOTDB-1685 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: Hai Liu >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 16h > Remaining Estimate: 16h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1680) Support Taosdb in iotdb-benchmark
[ https://issues.apache.org/jira/browse/IOTDB-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420450#comment-17420450 ] Xuan Ronaldo commented on IOTDB-1680: - [rename taosdb to tdengine and fix the support of tdengine by xuanronaldo · Pull Request #192 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/192] > Support Taosdb in iotdb-benchmark > - > > Key: IOTDB-1680 > URL: https://issues.apache.org/jira/browse/IOTDB-1680 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: FengQingxin >Assignee: Xuan Ronaldo >Priority: Minor > > Support Taosdb in iotdb-benchmark -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1728) Benchmark support 2 select operations in PI
[ https://issues.apache.org/jira/browse/IOTDB-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420451#comment-17420451 ] Xuan Ronaldo commented on IOTDB-1728: - [Support JDBC of PI Archive by xuanronaldo · Pull Request #196 · thulab/iotdb-benchmark (github.com)|https://github.com/thulab/iotdb-benchmark/pull/196] > Benchmark support 2 select operations in PI > --- > > Key: IOTDB-1728 > URL: https://issues.apache.org/jira/browse/IOTDB-1728 > Project: Apache IoTDB > Issue Type: New Feature > Components: Benchmark >Reporter: Hai Liu >Assignee: Xuan Ronaldo >Priority: Major > Original Estimate: 8h > Remaining Estimate: 8h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1618) The datetime-input format of the imported data is yyyy/MM/dd HH:mm:ss.SSS reports a null pointer
[ https://issues.apache.org/jira/browse/IOTDB-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420448#comment-17420448 ] Xuan Ronaldo commented on IOTDB-1618: - [[IOTDB-842] Better Export/Import-CSV Tool by xuanronaldo · Pull Request #3820 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/3820] > The datetime-input format of the imported data is /MM/dd HH:mm:ss.SSS > reports a null pointer > > > Key: IOTDB-1618 > URL: https://issues.apache.org/jira/browse/IOTDB-1618 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Affects Versions: master branch >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > Attachments: image-2021-09-09-17-21-48-402.png > > > data4.csv: > Time,Device,s1,s2,s3 > 2021/08/01/ 12:12:12.800,root.sg.d1,100,"M2",1000 > 2021/08/02/ 12:12:12.800,root.sg.d1,200,"M2",2000 > 2021/08/03/ 12:12:12.800,root.sg.d1,300,"M3",3000 > > The operation is as follows： > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ./tools/import-csv.sh > -h localhost -p 6667 -u root -pw root -f > /home/xzh/import-export/data/data4.csv > -- > Starting IoTDB Client Import Script > -- > 16:53:09.818 [main] DEBUG org.apache.iotdb.session.Session - > EndPoint(ip:localhost, port:6667) execute sql select * from root.sg.d1 limit 1 > Exception in thread "main" java.lang.NullPointerException > at org.apache.iotdb.tool.ImportCsv.lambda$null$5(ImportCsv.java:441) > at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) > at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) > at > java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at > java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at > java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) > at > java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) > at > org.apache.iotdb.tool.ImportCsv.lambda$writeDataAlignedByDevice$6(ImportCsv.java:399) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1553) > at > java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) > at > org.apache.iotdb.tool.ImportCsv.writeDataAlignedByDevice(ImportCsv.java:389) > at org.apache.iotdb.tool.ImportCsv.importFromSingleFile(ImportCsv.java:253) > at org.apache.iotdb.tool.ImportCsv.importFromTargetPath(ImportCsv.java:197) > at org.apache.iotdb.tool.ImportCsv.main(ImportCsv.java:171) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1621) By importing in yyyy.MM.dd HH:mm:ss.SSSZZ format to import data ,to find it mismatch in the CLI
[ https://issues.apache.org/jira/browse/IOTDB-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420447#comment-17420447 ] Xuan Ronaldo commented on IOTDB-1621: - [[IOTDB-842] Better Export/Import-CSV Tool by xuanronaldo · Pull Request #3820 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/3820] > By importing in .MM.dd HH:mm:ss.SSSZZ format to import data ,to find it > mismatch in the CLI > --- > > Key: IOTDB-1621 > URL: https://issues.apache.org/jira/browse/IOTDB-1621 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > Fix For: master branch > > Attachments: image-2021-09-06-10-40-49-743.png, > image-2021-09-06-10-41-10-522.png, image-2021-09-09-17-52-59-408.png > > > Import data as follow: > !image-2021-09-06-10-40-49-743.png! > Enter CLI to check: > !image-2021-09-06-10-41-10-522.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-842) Better Export/Import-CSV Tool
[
https://issues.apache.org/jira/browse/IOTDB-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420444#comment-17420444
]
Xuan Ronaldo commented on IOTDB-842:
[[IOTDB-842] Better Export/Import-CSV Tool by xuanronaldo · Pull Request #3820
· apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/3820]
> Better Export/Import-CSV Tool
> -
>
> Key: IOTDB-842
> URL: https://issues.apache.org/jira/browse/IOTDB-842
> Project: Apache IoTDB
> Issue Type: Task
> Components: Tools/Others
>Reporter: Xiangdong Huang
>Assignee: Xuan Ronaldo
>Priority: Major
> Labels: https://github.com/apache/iotdb/pull/3820,
> pull-request-available
>
> Hi, our import-csv tool is currently implemented by JDBC and requires a
> fossil format:
> e.g.,
> {code:java}
> Time,root.sg.d1.s1,root.sg.d1.s2,root.sg.d2.s1,root.sg.d2.s2,root.sg.d2.s3
> 2020-08-18T10:22:31.603+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:35.631+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:41.093+08:00,null,null,1,2.0,null
> 2020-08-18T10:22:52.603+08:00,null,null,1,2.0,true
> {code}
> Requirement 1:
> As we support 3 kinds of output format: align all series (by default), align
> by device, without alignment, it is better to support such 3 kinds of
> import-csv format:
> a.
> {code:java}
> Time,root.sg.d1.s1,root.sg.d1.s2,root.sg.d2.s1,root.sg.d2.s2,root.sg.d2.s3
> 2020-08-18T10:22:31.603+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:35.631+08:00,1,2.0,null,null,null
> 2020-08-18T10:22:41.093+08:00,null,null,1,2.0,null
> 2020-08-18T10:22:52.603+08:00,null,null,1,2.0,true
> {code}
> b.
> {code:java}
> Time,Device,s1,s2,s3
> 2020-08-18T10:22:31.603+08:00,root.sg.d1,1,2.0,null
> 2020-08-18T10:22:35.631+08:00,root.sg.d1,1,2.0,null
> 2020-08-18T10:22:41.093+08:00,root.sg.d2,1,2.0,null
> 2020-08-18T10:22:52.603+08:00,root.sg.d2,1,2.0,true
> {code}
> c.
> (it is strange, I'd like to do not support such format.)
> Requment2:
> Different users may have different time formats for the first column.
> So, we'd better support different kinds of time format. e.g., let users
> define how to parse their timestamp: -MM-ddHH:mm:ss.SSS etc..
> Requirement 3:
> Support NULL as well as empty char to describe the null data point. For
> example, the following 3 lines are the same:
> 2020-08-18T10:22:31.603+08:00,root.sg.d1,1,null,null
> 2020-08-18T10:22:31.603+08:00,root.sg.d1,1,,
> 2020-08-18T10:22:31.603+08:00,root.sg.d1,1,,
> Requirement 4:
> Support claiming the storage group name once rather than repeat the storage
> group name for each line:
> e.g., for format b, we can tell the tool the sg is `root.sg` and then each
> row looks like:
> 2020-08-18T10:22:35.631+08:00,d1,1,2.0,null
> Another option is add a new column called storage_group for each row.
> For UT:
> 1. all data type should be covered;
> 2. incorrect csv format should be covered;
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1563) Support disabling query timeout
[ https://issues.apache.org/jira/browse/IOTDB-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420445#comment-17420445 ] Xuan Ronaldo commented on IOTDB-1563: - [[IOTDB-842] Better Export/Import-CSV Tool by xuanronaldo · Pull Request #3820 · apache/iotdb (github.com)|https://github.com/apache/iotdb/pull/3820] > Support disabling query timeout > --- > > Key: IOTDB-1563 > URL: https://issues.apache.org/jira/browse/IOTDB-1563 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: Jialin Qiao >Assignee: Xuan Ronaldo >Priority: Minor > Labels: easy-fix, https://github.com/apache/iotdb/pull/3820 > > Currently, the query_timeout_threshold only could be set to a value >0. > We need to disable it when it is 0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1631) Timeout when exporting large data volume
[ https://issues.apache.org/jira/browse/IOTDB-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1631: --- Assignee: (was: Xuan Ronaldo) > Timeout when exporting large data volume > > > Key: IOTDB-1631 > URL: https://issues.apache.org/jira/browse/IOTDB-1631 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Reporter: xiaozhihong >Priority: Major > > Operate as follow: > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ls > conf data docs ext lib LICENSE licenses logs nohup.out NOTICE README.md > README_ZH.md RELEASE_NOTES.md sbin tools > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ./tools/export-csv.sh > -h 127.0.0.1 -p 6667 -u root -pw root -td /home/xzh/import-export/data/ > -- > Starting IoTDB Client Export Script > -- > ExportCsv> please input query: select * from root > select * from root > 16:04:27.897 [main] DEBUG org.apache.iotdb.session.Session - > EndPoint(ip:127.0.0.1, port:6667) execute sql select * from root > Cannot dump result because: 701: Current query is time out, please check your > statement or modify timeout parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1658) 0.12.2 RC2：The export-csv.sh tool does not support background running
[
https://issues.apache.org/jira/browse/IOTDB-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Ronaldo reassigned IOTDB-1658:
---
Assignee: Xuan Ronaldo
> 0.12.2 RC2：The export-csv.sh tool does not support background running
> -
>
> Key: IOTDB-1658
> URL: https://issues.apache.org/jira/browse/IOTDB-1658
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Tools/Others
>Reporter: 刘珍
>Assignee: Xuan Ronaldo
>Priority: Minor
> Attachments: image-2021-09-09-11-01-01-256.png
>
>
> /data/liuzhen_test/RC2_no_comp/tools/export-csv.sh -h 127.0.0.1 -p 6667 -u
> root -pw root -td /data/liuzhen_test/RC2_comp/test_shell/test_exp -f test_2_
> -s /data/liuzhen_test/RC2_comp/test_shell/sql/2.sql {color:#DE350B}*&*{color}
> !image-2021-09-09-11-01-01-256.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IOTDB-1621) By importing in yyyy.MM.dd HH:mm:ss.SSSZZ format to import data ,to find it mismatch in the CLI
[ https://issues.apache.org/jira/browse/IOTDB-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1621: --- Assignee: Xuan Ronaldo > By importing in .MM.dd HH:mm:ss.SSSZZ format to import data ,to find it > mismatch in the CLI > --- > > Key: IOTDB-1621 > URL: https://issues.apache.org/jira/browse/IOTDB-1621 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > Attachments: image-2021-09-06-10-40-49-743.png, > image-2021-09-06-10-41-10-522.png > > > Import data as follow: > !image-2021-09-06-10-40-49-743.png! > Enter CLI to check: > !image-2021-09-06-10-41-10-522.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1631) Timeout when exporting large data volume
[ https://issues.apache.org/jira/browse/IOTDB-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1631: --- Assignee: Xuan Ronaldo > Timeout when exporting large data volume > > > Key: IOTDB-1631 > URL: https://issues.apache.org/jira/browse/IOTDB-1631 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > > Operate as follow: > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ls > conf data docs ext lib LICENSE licenses logs nohup.out NOTICE README.md > README_ZH.md RELEASE_NOTES.md sbin tools > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ./tools/export-csv.sh > -h 127.0.0.1 -p 6667 -u root -pw root -td /home/xzh/import-export/data/ > -- > Starting IoTDB Client Export Script > -- > ExportCsv> please input query: select * from root > select * from root > 16:04:27.897 [main] DEBUG org.apache.iotdb.session.Session - > EndPoint(ip:127.0.0.1, port:6667) execute sql select * from root > Cannot dump result because: 701: Current query is time out, please check your > statement or modify timeout parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1618) The datetime-input format of the imported data is yyyy/MM/dd HH:mm:ss.SSS reports a null pointer
[ https://issues.apache.org/jira/browse/IOTDB-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Ronaldo reassigned IOTDB-1618: --- Assignee: Xuan Ronaldo > The datetime-input format of the imported data is /MM/dd HH:mm:ss.SSS > reports a null pointer > > > Key: IOTDB-1618 > URL: https://issues.apache.org/jira/browse/IOTDB-1618 > Project: Apache IoTDB > Issue Type: Bug > Components: Tools/Others >Affects Versions: master branch >Reporter: xiaozhihong >Assignee: Xuan Ronaldo >Priority: Major > > data4.csv: > Time,Device,s1,s2,s3 > 2021/08/01/ 12:12:12.800,root.sg.d1,100,"M2",1000 > 2021/08/02/ 12:12:12.800,root.sg.d1,200,"M2",2000 > 2021/08/03/ 12:12:12.800,root.sg.d1,300,"M3",3000 > > The operation is as follows： > [xzh@i-s9p350bm apache-iotdb-0.13.0-SNAPSHOT-all-bin]$ ./tools/import-csv.sh > -h localhost -p 6667 -u root -pw root -f > /home/xzh/import-export/data/data4.csv > -- > Starting IoTDB Client Import Script > -- > 16:53:09.818 [main] DEBUG org.apache.iotdb.session.Session - > EndPoint(ip:localhost, port:6667) execute sql select * from root.sg.d1 limit 1 > Exception in thread "main" java.lang.NullPointerException > at org.apache.iotdb.tool.ImportCsv.lambda$null$5(ImportCsv.java:441) > at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) > at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) > at > java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at > java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at > java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) > at > java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) > at > org.apache.iotdb.tool.ImportCsv.lambda$writeDataAlignedByDevice$6(ImportCsv.java:399) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1553) > at > java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) > at > org.apache.iotdb.tool.ImportCsv.writeDataAlignedByDevice(ImportCsv.java:389) > at org.apache.iotdb.tool.ImportCsv.importFromSingleFile(ImportCsv.java:253) > at org.apache.iotdb.tool.ImportCsv.importFromTargetPath(ImportCsv.java:197) > at org.apache.iotdb.tool.ImportCsv.main(ImportCsv.java:171) -- This message was sent by Atlassian Jira (v8.3.4#803005)
