[jira] [Created] (IOTDB-6137) Incorrect error message when the column in group by a
yang caiyin created IOTDB-6137: -- Summary: Incorrect error message when the column in group by a Key: IOTDB-6137 URL: https://issues.apache.org/jira/browse/IOTDB-6137 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin Attachments: image-2023-09-04-13-23-29-547.png !image-2023-09-04-13-23-29-547.png! the first parameter of group by variation() should be column instead of number, this info should be told to the user accurately -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6184) Merge Sort finish one iterator too late.
yang caiyin created IOTDB-6184: -- Summary: Merge Sort finish one iterator too late. Key: IOTDB-6184 URL: https://issues.apache.org/jira/browse/IOTDB-6184 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-10-10-18-22-07-777.png There is a wrong implementationo in MergeSortOperator !image-2023-10-10-18-22-07-777.png! If the code break too late, the smaller value behind tsBlock won't be filled in time, resulting in a wrong order. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6174) Support select __endTime in group by time when pushing down
[ https://issues.apache.org/jira/browse/IOTDB-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6174: -- Assignee: yang caiyin > Support select __endTime in group by time when pushing down > --- > > Key: IOTDB-6174 > URL: https://issues.apache.org/jira/browse/IOTDB-6174 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6174) Support select __endTime in group by time when pushing down
yang caiyin created IOTDB-6174: -- Summary: Support select __endTime in group by time when pushing down Key: IOTDB-6174 URL: https://issues.apache.org/jira/browse/IOTDB-6174 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6192) Redundant MergeSortOperator in ORDER BY TIME ALIGN BY DEVICE
yang caiyin created IOTDB-6192: -- Summary: Redundant MergeSortOperator in ORDER BY TIME ALIGN BY DEVICE Key: IOTDB-6192 URL: https://issues.apache.org/jira/browse/IOTDB-6192 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-10-16-17-18-49-995.png !image-2023-10-16-17-18-49-995.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6192) Redundant MergeSortOperator in ORDER BY TIME ALIGN BY DEVICE
[ https://issues.apache.org/jira/browse/IOTDB-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6192: -- Assignee: yang caiyin > Redundant MergeSortOperator in ORDER BY TIME ALIGN BY DEVICE > > > Key: IOTDB-6192 > URL: https://issues.apache.org/jira/browse/IOTDB-6192 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2023-10-16-17-18-49-995.png > > > !image-2023-10-16-17-18-49-995.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6120) push down limit/offset in query with group by time
[ https://issues.apache.org/jira/browse/IOTDB-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6120: -- Assignee: yang caiyin > push down limit/offset in query with group by time > -- > > Key: IOTDB-6120 > URL: https://issues.apache.org/jira/browse/IOTDB-6120 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > > 优化设计文档：https://apache-iotdb.feishu.cn/docx/TAsXd5hdZoVevrxqqgtcg9A9nhf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6120) push down limit/offset in query with group by time
yang caiyin created IOTDB-6120: -- Summary: push down limit/offset in query with group by time Key: IOTDB-6120 URL: https://issues.apache.org/jira/browse/IOTDB-6120 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin 优化设计文档：https://apache-iotdb.feishu.cn/docx/TAsXd5hdZoVevrxqqgtcg9A9nhf -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-3936) Add an interface in IClientRPCService to directly use TsBlock instead of TSQueryDataSet
[ https://issues.apache.org/jira/browse/IOTDB-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17617081#comment-17617081 ] yang caiyin commented on IOTDB-3936: To better solve this problem, besides executeStatementV2. We should also add fetchResultV2、executeRawDataQuery and executeLastDataQuery to replace the former method for a faster query without queryDataset. > Add an interface in IClientRPCService to directly use TsBlock instead of > TSQueryDataSet > --- > > Key: IOTDB-3936 > URL: https://issues.apache.org/jira/browse/IOTDB-3936 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Yuan Tian >Assignee: yang caiyin >Priority: Major > > Currently, we convert TsBlock to TSQueryDataSet to be compatible with > previous executeStatement() interface in IClientRPCService and in this way we > won't need to change all other language clients like go, C/C++ and python etc. > However, we can add a new interface like executeStatementV2 to directly > return serialized form of TsBlock to client and then do the deserialization > things in the client end. In this way, we can improve the query performance > if the result TsBlock is received from remote node. Because in such case, > what we received is already serialized TsBlock(in ByteBuffer form), we can > directly return that to client which will saving one deserializing TsBlock > and one serialzie to TSQueryDataSet. > We alse need to change the java client: jdbc and session to adapt to read > from TsBlock. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5278) JDBC Driver cannot connect to the dbeaver
yang caiyin created IOTDB-5278: -- Summary: JDBC Driver cannot connect to the dbeaver Key: IOTDB-5278 URL: https://issues.apache.org/jira/browse/IOTDB-5278 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin Fix For: master branch, 1.0.1 In the metaDataset of jdbc, the incorrect use of tsblockbuilder to generate result tsblock without timecolumn causes an error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5252) Optimization for MergeSortOperator
[ https://issues.apache.org/jira/browse/IOTDB-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649778#comment-17649778 ] yang caiyin commented on IOTDB-5252: The document of MergeSortOperator and ideas of optimization is https://apache-iotdb.feishu.cn/docx/NH65dpdgSoMV5OxAOEGcM6g1nEe > Optimization for MergeSortOperator > -- > > Key: IOTDB-5252 > URL: https://issues.apache.org/jira/browse/IOTDB-5252 > Project: Apache IoTDB > Issue Type: Task >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5341) The front end plan of eventWindow in aggregation query
yang caiyin created IOTDB-5341: -- Summary: The front end plan of eventWindow in aggregation query Key: IOTDB-5341 URL: https://issues.apache.org/jira/browse/IOTDB-5341 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Assignee: yang caiyin introduce eventWindow in a complete query procedure, which requires the sql parsing, statement analysing and logical plan -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5340) Backend of eventWindow in RawDataAggregationOperator
yang caiyin created IOTDB-5340: -- Summary: Backend of eventWindow in RawDataAggregationOperator Key: IOTDB-5340 URL: https://issues.apache.org/jira/browse/IOTDB-5340 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5144) ClassCastException in IoTDBDatabaseMetadata of jdbc
yang caiyin created IOTDB-5144: -- Summary: ClassCastException in IoTDBDatabaseMetadata of jdbc Key: IOTDB-5144 URL: https://issues.apache.org/jira/browse/IOTDB-5144 Project: Apache IoTDB Issue Type: Bug Components: Client/JDBC Reporter: yang caiyin Assignee: yang caiyin https://github.com/apache/iotdb/issues/8377 -- 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] [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-5200) Need additional judgement in getDoublue of IoTDBJDBCResultSet in IT
yang caiyin created IOTDB-5200: -- Summary: Need additional judgement in getDoublue of IoTDBJDBCResultSet in IT Key: IOTDB-5200 URL: https://issues.apache.org/jira/browse/IOTDB-5200 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin getInt、getDouble、getLong and getFloat in IoTDBJDBCResultSet will return 0 when the value is null which need an additional judgement on lastReadWasNull variable in IoTDBOrderByWithAlignByDeviceIT., -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5252) Optimization for MergeSortOperator
yang caiyin created IOTDB-5252: -- Summary: Optimization for MergeSortOperator Key: IOTDB-5252 URL: https://issues.apache.org/jira/browse/IOTDB-5252 Project: Apache IoTDB Issue Type: Task Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5114) Redundant planNode after distribution plan in raw data query with align by device
[ https://issues.apache.org/jira/browse/IOTDB-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5114: -- Assignee: yang caiyin > Redundant planNode after distribution plan in raw data query with align by > device > - > > Key: IOTDB-5114 > URL: https://issues.apache.org/jira/browse/IOTDB-5114 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2022-12-04-16-06-35-766.png > > > In the following raw data query explaining for a local series in 1C1D,only > one deviceViewNde is enough for the querying task. However in distribution > plan, a redundant deviceMergeNode is generated although there is only one > child of deiviceViewNode. > !image-2022-12-04-16-06-35-766.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5114) Redundant planNode after distribution plan in raw data query with align by device
yang caiyin created IOTDB-5114: -- Summary: Redundant planNode after distribution plan in raw data query with align by device Key: IOTDB-5114 URL: https://issues.apache.org/jira/browse/IOTDB-5114 Project: Apache IoTDB Issue Type: Improvement Components: Core/Server Reporter: yang caiyin Attachments: image-2022-12-04-16-06-35-766.png In the following raw data query explaining for a local series in 1C1D,only one deviceViewNde is enough for the querying task. However in distribution plan, a redundant deviceMergeNode is generated although there is only one child of deiviceViewNode. !image-2022-12-04-16-06-35-766.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5172) SingleDeviceViewNode can't get outputColumnTypes when it's isolated
yang caiyin created IOTDB-5172: -- Summary: SingleDeviceViewNode can't get outputColumnTypes when it's isolated Key: IOTDB-5172 URL: https://issues.apache.org/jira/browse/IOTDB-5172 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin Fix For: master branch Attachments: image-2022-12-11-17-16-01-243.png The SingleDeviceViewNode gets the outputColumnNames from MergeSortNode in LocalExecutionPlanner. However, in some situation such that only one SingleDeviceViewNode is assigned in data region, the lack of MergeSortNode will cause a null exception in visitSingleDeviceView. !image-2022-12-11-17-16-01-243.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5169) Add UserGuide for order by in align by device
yang caiyin created IOTDB-5169:
--
Summary: Add UserGuide for order by in align by device
Key: IOTDB-5169
URL: https://issues.apache.org/jira/browse/IOTDB-5169
Project: Apache IoTDB
Issue Type: Task
Reporter: yang caiyin
Assignee: yang caiyin
Fix For: master branch
UserGuide for {{[IOTDB-4572] [IOTDB-3580]}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4973) Improve the constructRowRecordFromValueArray in Session by holding timestamp in advance
[ https://issues.apache.org/jira/browse/IOTDB-4973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635589#comment-17635589 ] yang caiyin commented on IOTDB-4973: pull request: https://github.com/apache/iotdb/pull/8032 > Improve the constructRowRecordFromValueArray in Session by holding timestamp > in advance > --- > > Key: IOTDB-4973 > URL: https://issues.apache.org/jira/browse/IOTDB-4973 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Minor > > In SessionDataSet, constructRowRecordFromValueArray can be called frequently > when traversing the result. And the method used getTimeStamp to get time > value which cost extra time. > We can directly use a copy of time instead of calling the method in > constructRowRecordFromValueArray to reduce extra time cost. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4973) Improve the constructRowRecordFromValueArray in Session by holding timestamp in advance
yang caiyin created IOTDB-4973: -- Summary: Improve the constructRowRecordFromValueArray in Session by holding timestamp in advance Key: IOTDB-4973 URL: https://issues.apache.org/jira/browse/IOTDB-4973 Project: Apache IoTDB Issue Type: Improvement Reporter: yang caiyin Assignee: yang caiyin In SessionDataSet, constructRowRecordFromValueArray can be called frequently when traversing the result. In constructRow() method, we store a copy of the timestamp of currnet row but never used it. In constructRowRecordFromValueArray, we can directly use this copy instead of calling the method in TsBlock to reduce time cost. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4952) Client Deserialization time cost compare 1.0 vs 0.13
[ https://issues.apache.org/jira/browse/IOTDB-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635252#comment-17635252 ] yang caiyin commented on IOTDB-4952: the experiment result is in https://apache-iotdb.feishu.cn/docx/CKkgdhkpMoPmMoxrcCwcqOnlnxe > Client Deserialization time cost compare 1.0 vs 0.13 > > > Key: IOTDB-4952 > URL: https://issues.apache.org/jira/browse/IOTDB-4952 > Project: Apache IoTDB > Issue Type: Task >Reporter: Yuan Tian >Assignee: yang caiyin >Priority: Major > Attachments: image-2022-11-16-10-35-55-388.png > > > After profiling the query cost, we found that client derialization cost is > nonnegligible. > !image-2022-11-16-10-35-55-388.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5102) Get a null result when explain the sql using align by device
yang caiyin created IOTDB-5102: -- Summary: Get a null result when explain the sql using align by device Key: IOTDB-5102 URL: https://issues.apache.org/jira/browse/IOTDB-5102 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: yang caiyin Assignee: yang caiyin Attachments: image-2022-12-01-17-54-00-997.png !image-2022-12-01-17-54-00-997.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5340) Backend of eventWindow in RawDataAggregationOperator
[ https://issues.apache.org/jira/browse/IOTDB-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680903#comment-17680903 ] yang caiyin commented on IOTDB-5340: https://github.com/apache/iotdb/pull/7693 > Backend of eventWindow in RawDataAggregationOperator > > > Key: IOTDB-5340 > URL: https://issues.apache.org/jira/browse/IOTDB-5340 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5658) Support FetchTimeseries/RecordModelMetric in DataNodeInternalRPCService
[ https://issues.apache.org/jira/browse/IOTDB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reopened IOTDB-5658: > Support FetchTimeseries/RecordModelMetric in DataNodeInternalRPCService > --- > > Key: IOTDB-5658 > URL: https://issues.apache.org/jira/browse/IOTDB-5658 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5709) Support MlNodeInteralRPCService in DataNode
yang caiyin created IOTDB-5709: -- Summary: Support MlNodeInteralRPCService in DataNode Key: IOTDB-5709 URL: https://issues.apache.org/jira/browse/IOTDB-5709 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5658) Support FetchTimeseries in DataNodeInternalRPCService
yang caiyin created IOTDB-5658: -- Summary: Support FetchTimeseries in DataNodeInternalRPCService Key: IOTDB-5658 URL: https://issues.apache.org/jira/browse/IOTDB-5658 Project: Apache IoTDB Issue Type: Improvement Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5554) Support group by session in aggregation query.
yang caiyin created IOTDB-5554: -- Summary: Support group by session in aggregation query. Key: IOTDB-5554 URL: https://issues.apache.org/jira/browse/IOTDB-5554 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5563) Optimization the framework of GroupBy
yang caiyin created IOTDB-5563: -- Summary: Optimization the framework of GroupBy Key: IOTDB-5563 URL: https://issues.apache.org/jira/browse/IOTDB-5563 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5580) Add limitation of time and size of resultTsBlock to return in advance for MergeSortOperator
yang caiyin created IOTDB-5580: -- Summary: Add limitation of time and size of resultTsBlock to return in advance for MergeSortOperator Key: IOTDB-5580 URL: https://issues.apache.org/jira/browse/IOTDB-5580 Project: Apache IoTDB Issue Type: Improvement Reporter: yang caiyin Assignee: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5572) Typo in GroupBy-UserGuide
yang caiyin created IOTDB-5572: -- Summary: Typo in GroupBy-UserGuide Key: IOTDB-5572 URL: https://issues.apache.org/jira/browse/IOTDB-5572 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin https://iotdb.apache.org/zh/UserGuide/Master/Query-Data/Group-By.html#%E6%97%B6%E9%97%B4%E5%8C%BA%E9%97%B4%E5%88%86%E6%AE%B5%E8%81%9A%E5%90%88 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5785) NPE in TransformOperator when input column is expression
yang caiyin created IOTDB-5785:
--
Summary: NPE in TransformOperator when input column is expression
Key: IOTDB-5785
URL: https://issues.apache.org/jira/browse/IOTDB-5785
Project: Apache IoTDB
Issue Type: Bug
Reporter: yang caiyin
使用分支代码[https://github.com/ycycse/iotdb/tree/orderByTransformError]
启动1C1D，写入以下数据
{code:java}
CREATE DATABASE root.sg;
CREATE TIMESERIES root.sg.d.num WITH DATATYPE=INT32, ENCODING=RLE;
CREATE TIMESERIES root.sg.d.bigNum WITH DATATYPE=INT64, ENCODING=RLE;
CREATE TIMESERIES root.sg.d.floatNum WITH DATATYPE=DOUBLE, ENCODING=RLE,
'MAX_POINT_NUMBER'='4';
CREATE TIMESERIES root.sg.d.str WITH DATATYPE=TEXT, ENCODING=PLAIN;
CREATE TIMESERIES root.sg.d.bool WITH DATATYPE=BOOLEAN, ENCODING=PLAIN;
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(0,3,2947483648,231.2121,"coconut",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(20,2,2147483648,434.12,"pineapple",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(40,1,2247483648,12.123,"apricot",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(80,9,2147483646,43.12,"apple",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(100,8,2147483964,4654.231,"papaya",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(3153600,6,2147483650,1231.21,"banana",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(31536000100,10,3147483648,231.55,"pumelo",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(31536000500,4,2147493648,213.1,"peach",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(31536001000,5,2149783648,56.32,"orange",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(3153601,7,2147983648,213.112,"lemon",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(3153610,11,2147468648,54.121,"pitaya",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(4153600,12,2146483648,45.231,"strawberry",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(4153620,14,2907483648,231.34,"cherry",FALSE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(4153690,13,2107483648,54.12,"lychee",TRUE);
insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
values(5153600,15,3147483648,235.213,"watermelon",TRUE);{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5785) NPE in TransformOperator when input column is expression
[
https://issues.apache.org/jira/browse/IOTDB-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yang caiyin reassigned IOTDB-5785:
--
Assignee: (was: yang caiyin)
> NPE in TransformOperator when input column is expression
>
>
> Key: IOTDB-5785
> URL: https://issues.apache.org/jira/browse/IOTDB-5785
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: yang caiyin
>Priority: Major
> Attachments: image-2023-04-18-15-22-43-955.png,
> image-2023-04-18-15-23-34-326.png
>
>
> 使用分支代码[https://github.com/ycycse/iotdb/tree/orderByTransformError]
> 启动1C1D，写入以下数据
> {code:java}
> CREATE DATABASE root.sg;
> CREATE TIMESERIES root.sg.d.num WITH DATATYPE=INT32, ENCODING=RLE;
> CREATE TIMESERIES root.sg.d.bigNum WITH DATATYPE=INT64, ENCODING=RLE;
> CREATE TIMESERIES root.sg.d.floatNum WITH DATATYPE=DOUBLE, ENCODING=RLE,
> 'MAX_POINT_NUMBER'='4';
> CREATE TIMESERIES root.sg.d.str WITH DATATYPE=TEXT, ENCODING=PLAIN;
> CREATE TIMESERIES root.sg.d.bool WITH DATATYPE=BOOLEAN, ENCODING=PLAIN;
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(0,3,2947483648,231.2121,"coconut",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(20,2,2147483648,434.12,"pineapple",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(40,1,2247483648,12.123,"apricot",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(80,9,2147483646,43.12,"apple",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(100,8,2147483964,4654.231,"papaya",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153600,6,2147483650,1231.21,"banana",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536000100,10,3147483648,231.55,"pumelo",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536000500,4,2147493648,213.1,"peach",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536001000,5,2149783648,56.32,"orange",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153601,7,2147983648,213.112,"lemon",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153610,11,2147468648,54.121,"pitaya",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153600,12,2146483648,45.231,"strawberry",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153620,14,2907483648,231.34,"cherry",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153690,13,2107483648,54.12,"lychee",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(5153600,15,3147483648,235.213,"watermelon",TRUE);{code}
> 使用带表达式的查询
>
> {code:java}
> select num+bigNum from root.sg.d order by num+floatNum{code}
> 获得如下报错信息
>
> !image-2023-04-18-15-22-43-955.png!
> 查询计划如下所示
> !image-2023-04-18-15-23-34-326.png!
> 原因应是第二个TransformNode的输入为表达式，在OperatorTreeGenerator阶段解析错误。
> 类似
> {code:java}
> select avg(num)+sum(floatNum) from root.sg.d group by session(1ms) order
> by sum(num)；
> select num+bigNum,floatNum from root.sg.d order by str；{code}
> 等需要先进行一次转换再投影的查询，都有类似的问题（order by 后面的表达式不出现在select中时）
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-5785) NPE in TransformOperator when input column is expression
[
https://issues.apache.org/jira/browse/IOTDB-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yang caiyin reassigned IOTDB-5785:
--
Assignee: yang caiyin
> NPE in TransformOperator when input column is expression
>
>
> Key: IOTDB-5785
> URL: https://issues.apache.org/jira/browse/IOTDB-5785
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: yang caiyin
>Assignee: yang caiyin
>Priority: Major
> Attachments: image-2023-04-18-15-22-43-955.png,
> image-2023-04-18-15-23-34-326.png
>
>
> 使用分支代码[https://github.com/ycycse/iotdb/tree/orderByTransformError]
> 启动1C1D，写入以下数据
> {code:java}
> CREATE DATABASE root.sg;
> CREATE TIMESERIES root.sg.d.num WITH DATATYPE=INT32, ENCODING=RLE;
> CREATE TIMESERIES root.sg.d.bigNum WITH DATATYPE=INT64, ENCODING=RLE;
> CREATE TIMESERIES root.sg.d.floatNum WITH DATATYPE=DOUBLE, ENCODING=RLE,
> 'MAX_POINT_NUMBER'='4';
> CREATE TIMESERIES root.sg.d.str WITH DATATYPE=TEXT, ENCODING=PLAIN;
> CREATE TIMESERIES root.sg.d.bool WITH DATATYPE=BOOLEAN, ENCODING=PLAIN;
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(0,3,2947483648,231.2121,"coconut",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(20,2,2147483648,434.12,"pineapple",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(40,1,2247483648,12.123,"apricot",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(80,9,2147483646,43.12,"apple",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(100,8,2147483964,4654.231,"papaya",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153600,6,2147483650,1231.21,"banana",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536000100,10,3147483648,231.55,"pumelo",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536000500,4,2147493648,213.1,"peach",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(31536001000,5,2149783648,56.32,"orange",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153601,7,2147983648,213.112,"lemon",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(3153610,11,2147468648,54.121,"pitaya",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153600,12,2146483648,45.231,"strawberry",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153620,14,2907483648,231.34,"cherry",FALSE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(4153690,13,2107483648,54.12,"lychee",TRUE);
> insert into root.sg.d(timestamp,num,bigNum,floatNum,str,bool)
> values(5153600,15,3147483648,235.213,"watermelon",TRUE);{code}
> 使用带表达式的查询
>
> {code:java}
> select num+bigNum from root.sg.d order by num+floatNum{code}
> 获得如下报错信息
>
> !image-2023-04-18-15-22-43-955.png!
> 查询计划如下所示
> !image-2023-04-18-15-23-34-326.png!
> 原因应是第二个TransformNode的输入为表达式，在OperatorTreeGenerator阶段解析错误。
> 类似
> {code:java}
> select avg(num)+sum(floatNum) from root.sg.d group by session(1ms) order
> by sum(num)；
> select num+bigNum,floatNum from root.sg.d order by str；{code}
> 等需要先进行一次转换再投影的查询，都有类似的问题（order by 后面的表达式不出现在select中时）
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5804) [MLNODE] Support fetchWindowBatch in MLNodeInternalRpcService
yang caiyin created IOTDB-5804: -- Summary: [MLNODE] Support fetchWindowBatch in MLNodeInternalRpcService Key: IOTDB-5804 URL: https://issues.apache.org/jira/browse/IOTDB-5804 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5747) UDF SlidingTimeWindow slidingStep bug
[ https://issues.apache.org/jira/browse/IOTDB-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5747: -- Assignee: yang caiyin > UDF SlidingTimeWindow slidingStep bug > - > > Key: IOTDB-5747 > URL: https://issues.apache.org/jira/browse/IOTDB-5747 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Lei Rui >Assignee: yang caiyin >Priority: Major > > To reproduce the bug in IoTDB v1.0.1: > ``` > insert into root.sg1.d1(timestamp,s1) values(1,1) > insert into root.sg1.d1(timestamp,s1) values(2,2) > insert into root.sg1.d1(timestamp,s1) values(3,3) > insert into root.sg1.d1(timestamp,s1) values(4,4) > insert into root.sg1.d1(timestamp,s1) values(5,5) > insert into root.sg1.d1(timestamp,s1) values(6,6) > insert into root.sg1.d1(timestamp,s1) values(7,7) > insert into root.sg1.d1(timestamp,s1) values(8,8) > select M4(s1,'timeInterval'='3','slidingStep'='2') from root.sg1.d1 > ``` > The query result is: > ``` > +-+-+ > | Time|M4(root.sg1.d1.s1, "timeInterval"="3", > "slidingStep"="2")| > +-+-+ > |1970-01-01T08:00:00.001+08:00| >1.0| > |1970-01-01T08:00:00.003+08:00| >3.0| > +-+-+ > Total line number = 2 > ``` > which is wrong, as the sliding time windows and the M4 samples of each window > should be: > - [1,4): samples (1,1),(3,3) > - [3,6): samples (3,3),(5,5) > - [5,8): samples (5,5), (7,7) > - [7,10): samples (7,7), (8,8) > From my observation, the bug tends to happen when the slidingStep equals > timeInterval-1. I think there are bugs in the sliding time window code, but I > couldn't locate the bug because I am not familiar with the UDF module. > By the way, IoTDB version is: > ``` > IoTDB> show version > +---+---+ > |Version| BuildInfo| > +---+---+ > | 1.0.1|88c9bef-dev| > +---+---+ > ``` > I used the released apache-iotdb-1.0.1-all-bin zip. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5765) Support Order By Expression
yang caiyin created IOTDB-5765: -- Summary: Support Order By Expression Key: IOTDB-5765 URL: https://issues.apache.org/jira/browse/IOTDB-5765 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Assignee: yang caiyin https://apache-iotdb.feishu.cn/docx/Cqp6dhiEVoUakGx0wg1clGGlneg -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5484) The design of GROUP BY SERIES
yang caiyin created IOTDB-5484: -- Summary: The design of GROUP BY SERIES Key: IOTDB-5484 URL: https://issues.apache.org/jira/browse/IOTDB-5484 Project: Apache IoTDB Issue Type: Task Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5484) The design of GROUP BY SERIES
[ https://issues.apache.org/jira/browse/IOTDB-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685073#comment-17685073 ] yang caiyin commented on IOTDB-5484: https://apache-iotdb.feishu.cn/docx/N1Mmd3HWyoDjohxCO9ic6JO2nXc > The design of GROUP BY SERIES > - > > Key: IOTDB-5484 > URL: https://issues.apache.org/jira/browse/IOTDB-5484 > Project: Apache IoTDB > Issue Type: Task >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5484) The design of GROUP BY SERIES
[ https://issues.apache.org/jira/browse/IOTDB-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5484: -- Assignee: yang caiyin > The design of GROUP BY SERIES > - > > Key: IOTDB-5484 > URL: https://issues.apache.org/jira/browse/IOTDB-5484 > Project: Apache IoTDB > Issue Type: Task >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5486) The transformation from binary tsblock to numpy.ndarray
[ https://issues.apache.org/jira/browse/IOTDB-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5486: -- Assignee: yang caiyin > The transformation from binary tsblock to numpy.ndarray > --- > > Key: IOTDB-5486 > URL: https://issues.apache.org/jira/browse/IOTDB-5486 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5230) LogicPlan for window functions
[ https://issues.apache.org/jira/browse/IOTDB-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17685072#comment-17685072 ] yang caiyin commented on IOTDB-5230: https://github.com/apache/iotdb/commit/cf5a51a5e82c4a5b31fb7ae3a72663f2e63a8bf7 > 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 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5486) The transformation from binary tsblock to numpy.ndarray
yang caiyin created IOTDB-5486: -- Summary: The transformation from binary tsblock to numpy.ndarray Key: IOTDB-5486 URL: https://issues.apache.org/jira/browse/IOTDB-5486 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5515) Support group by series in aggregation query.
yang caiyin created IOTDB-5515: -- Summary: Support group by series in aggregation query. Key: IOTDB-5515 URL: https://issues.apache.org/jira/browse/IOTDB-5515 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin user guide: https://apache-iotdb.feishu.cn/docx/NgCXdVmPSoTdZsx3TzNcF0J9n6d deign doc: https://apache-iotdb.feishu.cn/docx/N1Mmd3HWyoDjohxCO9ic6JO2nXc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5515) Support group by series in aggregation query.
[ https://issues.apache.org/jira/browse/IOTDB-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5515: -- Assignee: yang caiyin > Support group by series in aggregation query. > - > > Key: IOTDB-5515 > URL: https://issues.apache.org/jira/browse/IOTDB-5515 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > > user guide: > https://apache-iotdb.feishu.cn/docx/NgCXdVmPSoTdZsx3TzNcF0J9n6d > deign doc: > https://apache-iotdb.feishu.cn/docx/N1Mmd3HWyoDjohxCO9ic6JO2nXc > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6069) Support SessionPool in client-py
yang caiyin created IOTDB-6069: -- Summary: Support SessionPool in client-py Key: IOTDB-6069 URL: https://issues.apache.org/jira/browse/IOTDB-6069 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5930) Support Order by in Last Query
yang caiyin created IOTDB-5930: -- Summary: Support Order by in Last Query Key: IOTDB-5930 URL: https://issues.apache.org/jira/browse/IOTDB-5930 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5960) Exception of GroupByCount in 1C3D
yang caiyin created IOTDB-5960: -- Summary: Exception of GroupByCount in 1C3D Key: IOTDB-5960 URL: https://issues.apache.org/jira/browse/IOTDB-5960 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin Attachments: image-2023-06-01-09-49-28-732.png !image-2023-06-01-09-49-28-732.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5960) Exception of GroupByCount in 1C3D
[ https://issues.apache.org/jira/browse/IOTDB-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5960: -- Assignee: yang caiyin > Exception of GroupByCount in 1C3D > - > > Key: IOTDB-5960 > URL: https://issues.apache.org/jira/browse/IOTDB-5960 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2023-06-01-09-49-28-732.png > > > !image-2023-06-01-09-49-28-732.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5970) Fix the info of ORDER BY when sortkey doesn't exist
[ https://issues.apache.org/jira/browse/IOTDB-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5970: -- Assignee: yang caiyin > Fix the info of ORDER BY when sortkey doesn't exist > --- > > Key: IOTDB-5970 > URL: https://issues.apache.org/jira/browse/IOTDB-5970 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2023-06-05-10-57-19-011.png > > > !image-2023-06-05-10-57-19-011.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5970) Fix the info of ORDER BY when sortkey doesn't exist
yang caiyin created IOTDB-5970: -- Summary: Fix the info of ORDER BY when sortkey doesn't exist Key: IOTDB-5970 URL: https://issues.apache.org/jira/browse/IOTDB-5970 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-06-05-10-57-19-011.png !image-2023-06-05-10-57-19-011.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5982) Modify the docs of Group By
yang caiyin created IOTDB-5982: -- Summary: Modify the docs of Group By Key: IOTDB-5982 URL: https://issues.apache.org/jira/browse/IOTDB-5982 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5982) Modify the docs of Group By
[ https://issues.apache.org/jira/browse/IOTDB-5982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-5982: -- Assignee: yang caiyin > Modify the docs of Group By > --- > > Key: IOTDB-5982 > URL: https://issues.apache.org/jira/browse/IOTDB-5982 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5983) Unclear info in group by clause when there is wrong expression
yang caiyin created IOTDB-5983: -- Summary: Unclear info in group by clause when there is wrong expression Key: IOTDB-5983 URL: https://issues.apache.org/jira/browse/IOTDB-5983 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Assignee: yang caiyin Attachments: image-2023-06-09-11-14-59-539.png !image-2023-06-09-11-14-59-539.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6069) Support SessionPool in client-py
[ https://issues.apache.org/jira/browse/IOTDB-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6069: -- Assignee: yang caiyin > Support SessionPool in client-py > > > Key: IOTDB-6069 > URL: https://issues.apache.org/jira/browse/IOTDB-6069 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > > *docs:* > https://iotdb.staged.apache.org/zh/UserGuide/V1.2.x/API/Programming-Python-Native-API.html#%E5%88%9D%E5%A7%8B%E5%8C%96 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6274) Bug in Group by month
yang caiyin created IOTDB-6274: -- Summary: Bug in Group by month Key: IOTDB-6274 URL: https://issues.apache.org/jira/browse/IOTDB-6274 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin Attachments: image-2023-12-21-18-01-42-411.png # can't query with group by month + limit/offset # Group by month calculate the wrong results. # Can't use __endTime in GROUP BY TIME + ALIGN BY DEVICE The right way to calcute the time results in group by month should be (startTime + count*MonDuration + nonMonDuration*count, endTime + (count+intervalNum)*MonDuration + nonMonDuration*(count+intervalNum)] which can't be accumulative. Example(red is the right result): !image-2023-12-21-18-01-42-411.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6274) Bug in Group by month
[ https://issues.apache.org/jira/browse/IOTDB-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6274: -- Assignee: yang caiyin > Bug in Group by month > - > > Key: IOTDB-6274 > URL: https://issues.apache.org/jira/browse/IOTDB-6274 > Project: Apache IoTDB > Issue Type: Bug >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Attachments: image-2023-12-21-18-01-42-411.png > > > # can't query with group by month + limit/offset > # Group by month calculate the wrong results. > # Can't use __endTime in GROUP BY TIME + ALIGN BY DEVICE > > The right way to calcute the time results in group by month should be > (startTime + count*MonDuration + nonMonDuration*count, endTime + > (count+intervalNum)*MonDuration + nonMonDuration*(count+intervalNum)] which > can't be accumulative. > Example(red is the right result): > !image-2023-12-21-18-01-42-411.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6325) Activate metadata query in SHOW/COUNT TIMESERIES/DEVICES
yang caiyin created IOTDB-6325: -- Summary: Activate metadata query in SHOW/COUNT TIMESERIES/DEVICES Key: IOTDB-6325 URL: https://issues.apache.org/jira/browse/IOTDB-6325 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin metadata query with time condition -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6325) Activate metadata query in SHOW/COUNT TIMESERIES/DEVICES
[ https://issues.apache.org/jira/browse/IOTDB-6325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6325: -- Assignee: yang caiyin > Activate metadata query in SHOW/COUNT TIMESERIES/DEVICES > > > Key: IOTDB-6325 > URL: https://issues.apache.org/jira/browse/IOTDB-6325 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > > metadata query with time condition -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6314) Optimization won't work in ExplainAnzlye
yang caiyin created IOTDB-6314: -- Summary: Optimization won't work in ExplainAnzlye Key: IOTDB-6314 URL: https://issues.apache.org/jira/browse/IOTDB-6314 Project: Apache IoTDB Issue Type: Bug Reporter: yang caiyin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6304) Support EXPLAIN ANALYZE in IoTDB
[ https://issues.apache.org/jira/browse/IOTDB-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yang caiyin reassigned IOTDB-6304: -- Assignee: yang caiyin > Support EXPLAIN ANALYZE in IoTDB > > > Key: IOTDB-6304 > URL: https://issues.apache.org/jira/browse/IOTDB-6304 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yang caiyin >Assignee: yang caiyin >Priority: Major > > https://apache-iotdb.feishu.cn/docx/JpCpdw1rKoVSBLxgy7Ucey7rn7f -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6304) Support EXPLAIN ANALYZE in IoTDB
yang caiyin created IOTDB-6304: -- Summary: Support EXPLAIN ANALYZE in IoTDB Key: IOTDB-6304 URL: https://issues.apache.org/jira/browse/IOTDB-6304 Project: Apache IoTDB Issue Type: New Feature Reporter: yang caiyin https://apache-iotdb.feishu.cn/docx/JpCpdw1rKoVSBLxgy7Ucey7rn7f -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-6335) Redundant rows when using GROUP BY TIME with LIMIT
[
https://issues.apache.org/jira/browse/IOTDB-6335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851489#comment-17851489
]
yang caiyin commented on IOTDB-6335:
After analysis, the problem occurs due to the bug in limit/offset push down to
GroupBy parameter.
In the following logic, we want to calculate the new startTime after skip some
points, but if size is smaller the size calculated, startTime will be negative
which leads to problem.
!image-2024-06-03-11-26-32-473.png!
> Redundant rows when using GROUP BY TIME with LIMIT
> --
>
> Key: IOTDB-6335
> URL: https://issues.apache.org/jira/browse/IOTDB-6335
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query
>Reporter: yang caiyin
>Assignee: yang caiyin
>Priority: Major
> Attachments: image-2024-06-03-11-26-32-473.png
>
>
> When using {{{}GROUP BY time + LIMIT{}}}, if the number of {{LIMIT}} exceeds
> the number of existing time intervals, it will generate excess time intervals.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6335) Redundant rows when using GROUP BY TIME with LIMIT
yang caiyin created IOTDB-6335:
--
Summary: Redundant rows when using GROUP BY TIME with LIMIT
Key: IOTDB-6335
URL: https://issues.apache.org/jira/browse/IOTDB-6335
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: yang caiyin
Assignee: yang caiyin
When using {{{}GROUP BY time + LIMIT{}}}, if the number of {{LIMIT}} exceeds
the number of existing time intervals, it will generate excess time intervals.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-6337) Wrong header in show active metadata when schema is empty.
[
https://issues.apache.org/jira/browse/IOTDB-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852283#comment-17852283
]
yang caiyin commented on IOTDB-6337:
BTW, I found the logic of pushing down count calculation to RegionScan Operator
is missing. I also support that in this issue.
> Wrong header in show active metadata when schema is empty.
> --
>
> Key: IOTDB-6337
> URL: https://issues.apache.org/jira/browse/IOTDB-6337
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query
>Reporter: yang caiyin
>Assignee: yang caiyin
>Priority: Major
>
> In general metaQuery, if the schema is empty, we may get the following
> results (/):
> {code:java}
> IoTDB> show timeseries
> +--+-++++---++--++--++
> |Timeseries|Alias|Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|ViewType|
> +--+-++++---++--++--++
> +--+-++++---++--++--++
> IoTDB> show devices
> +--+-++---+
> |Device|IsAligned|Template|TTL|
> +--+-++---+
> +--+-++---+
> IoTDB> count timeseries
> +-+
> |count(timeseries)|
> +-+
> | 0|
> +-+
> IoTDB> count devices
> +--+
> |count(devices)|
> +--+
> | 0|
> +--+
> {code}
> But in active metadata query, we get the following confusing results :(
> {code:java}
> IoTDB> show timeseries where time < 6
> ++
> |Time|
> ++
> ++
> IoTDB> show devices where time < 6
> ++
> |Time|
> ++
> ++
> IoTDB> count timeseries where time < 6
> Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count timeseries
> where time < 6". executeStatement failed. null
> IoTDB> count devices where time < 6
> Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count devices
> where time < 6". executeStatement failed. null{code}
> We should fix and unify these. (flag)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-6337) Wrong header in show active metadata when result is empty.
[
https://issues.apache.org/jira/browse/IOTDB-6337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yang caiyin reassigned IOTDB-6337:
--
Assignee: yang caiyin
> Wrong header in show active metadata when result is empty.
> --
>
> Key: IOTDB-6337
> URL: https://issues.apache.org/jira/browse/IOTDB-6337
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Query
>Reporter: yang caiyin
>Assignee: yang caiyin
>Priority: Major
>
> In general metaQuery, if the resultSet is empty, we may get the following
> results (/):
> {code:java}
> IoTDB> show timeseries
> +--+-++++---++--++--++
> |Timeseries|Alias|Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|ViewType|
> +--+-++++---++--++--++
> +--+-++++---++--++--++
> IoTDB> show devices
> +--+-++---+
> |Device|IsAligned|Template|TTL|
> +--+-++---+
> +--+-++---+
> IoTDB> count timeseries
> +-+
> |count(timeseries)|
> +-+
> | 0|
> +-+
> IoTDB> count devices
> +--+
> |count(devices)|
> +--+
> | 0|
> +--+
> {code}
> But in active metadata query, we get the following confusing results :(
> {code:java}
> IoTDB> show timeseries where time < 6
> ++
> |Time|
> ++
> ++
> IoTDB> show devices where time < 6
> ++
> |Time|
> ++
> ++
> IoTDB> count timeseries where time < 6
> Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count timeseries
> where time < 6". executeStatement failed. null
> IoTDB> count devices where time < 6
> Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count devices
> where time < 6". executeStatement failed. null{code}
> We should fix and unify these. (flag)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6337) Wrong header in show active metadata when result is empty.
yang caiyin created IOTDB-6337:
--
Summary: Wrong header in show active metadata when result is empty.
Key: IOTDB-6337
URL: https://issues.apache.org/jira/browse/IOTDB-6337
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: yang caiyin
In general metaQuery, if the resultSet is empty, we may get the following
results (/):
{code:java}
IoTDB> show timeseries
+--+-++++---++--++--++
|Timeseries|Alias|Database|DataType|Encoding|Compression|Tags|Attributes|Deadband|DeadbandParameters|ViewType|
+--+-++++---++--++--++
+--+-++++---++--++--++
IoTDB> show devices
+--+-++---+
|Device|IsAligned|Template|TTL|
+--+-++---+
+--+-++---+
IoTDB> count timeseries
+-+
|count(timeseries)|
+-+
| 0|
+-+
IoTDB> count devices
+--+
|count(devices)|
+--+
| 0|
+--+
{code}
But in active metadata query, we get the following confusing results :(
{code:java}
IoTDB> show timeseries where time < 6
++
|Time|
++
++
IoTDB> show devices where time < 6
++
|Time|
++
++
IoTDB> count timeseries where time < 6
Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count timeseries
where time < 6". executeStatement failed. null
IoTDB> count devices where time < 6
Msg: 305: [INTERNAL_SERVER_ERROR(305)] Exception occurred: "count devices where
time < 6". executeStatement failed. null{code}
We should fix and unify these. (flag)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
