[jira] [Commented] (IOTDB-1212) select sin(not_exist) from root.sg1.d1; The error message is not right.
[
https://issues.apache.org/jira/browse/IOTDB-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335316#comment-17335316
]
刘珍 commented on IOTDB-1212:
---
通过。rel/0.12
git log
commit f74425589e2f7211d8bd318fb95607c602d8a923
Author: Zesong Sun
Date: Thu Apr 29 17:45:01 2021 +0800
Add TsFileSequenceReader getChunkMetadataList method return empty if path not
exists (#3111)
commit d979bfd3cc2c4fd78b1890b73c61e73599b43c5d
Author: Steve Yurong Su
Date: Thu Apr 29 17:39:35 2021 +0800
[To rel/0.12][IOTDB-1212] The given error message is not right when executing
`select sin(non_existence) from root.sg1.d1` (#3102)
!image-2021-04-29-18-00-30-051.png!
> select sin(not_exist) from root.sg1.d1; The error message is not right.
>
>
> Key: IOTDB-1212
> URL: https://issues.apache.org/jira/browse/IOTDB-1212
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/Java
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Fix For: 0.12.1
>
> Attachments: image-2021-04-29-18-00-30-051.png
>
>
> master branch
> commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
>
> SET STORAGE GROUP TO root.sg1;
> CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
> CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (0, -1, 1);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (1, -2, 2);
> INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (2, -3, 3);
> select sin(not_exist) from root.sg1.d1;
>
> Msg: 411: Error occurred in query process: Error occurred during executing
> UDTF#validate(UDFParameterValidator):
> {color:#FF}org.apache.iotdb.db.query.udf.api.exception.UDFInputSeriesNumberNotValidException:
> the number of the input series is not valid. expected: 1. actual: 0.{color}
> {color:#FF}The error message is not right.{color}
> {color:#ff}The actual is the input series does not exist.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IOTDB-843) Add a new datatype String with specified length
[ https://issues.apache.org/jira/browse/IOTDB-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-843: Assignee: (was: Haonan Hou) > Add a new datatype String with specified length > --- > > Key: IOTDB-843 > URL: https://issues.apache.org/jira/browse/IOTDB-843 > Project: Apache IoTDB > Issue Type: New Feature > Components: Core/Engine >Reporter: Haonan Hou >Priority: Major > > As many other DBs, we should support String with specified maximum length as > a new data type. This type of string data can be managed by array pool and > easy to control the memory cost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1347) Unseq compaction throws wrong exception if some paths are not in the file
Zesong Sun created IOTDB-1347: - Summary: Unseq compaction throws wrong exception if some paths are not in the file Key: IOTDB-1347 URL: https://issues.apache.org/jira/browse/IOTDB-1347 Project: Apache IoTDB Issue Type: Bug Reporter: Zesong Sun Assignee: Zesong Sun Fix For: 0.12.1, 0.13.0 Attachments: image-2021-04-29-17-22-41-770.png Unseq compaction failed if some path not in the file, throw error like below. !image-2021-04-29-17-22-41-770.png|width=579,height=168! Reason: The getChunkMetadataList now throw Exception if there is not the path in the file. Solution: Add a method getChunkMetadataListReturnEmptyIfPathNotExists and use it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1346) The configuration timeout parameter is only limited to an integer
xiaozhihong created IOTDB-1346: -- Summary: The configuration timeout parameter is only limited to an integer Key: IOTDB-1346 URL: https://issues.apache.org/jira/browse/IOTDB-1346 Project: Apache IoTDB Issue Type: Improvement Components: Document Reporter: xiaozhihong In the User Guide: Query timeout ,modify the timeout paramete,add to just an integer. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1342) Verify that LIMIT and OFFSET are used in conjunction with the FILL clause, and the error message is inconsistent with the system service
[ https://issues.apache.org/jira/browse/IOTDB-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335238#comment-17335238 ] xiaozhihong commented on IOTDB-1342: location：DML Example 4: LIMIT clause combined with GROUP BY clause Error Handling !image-2021-04-29-16-27-15-149.png|width=612,height=183! > Verify that LIMIT and OFFSET are used in conjunction with the FILL clause, > and the error message is inconsistent with the system service > > > Key: IOTDB-1342 > URL: https://issues.apache.org/jira/browse/IOTDB-1342 > Project: Apache IoTDB > Issue Type: Bug > Components: Document >Affects Versions: 0.12.0 >Reporter: xiaozhihong >Priority: Trivial > Attachments: image-2021-04-29-15-03-40-134.png, > image-2021-04-29-16-27-15-149.png > > > !image-2021-04-29-15-03-40-134.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IOTDB-1330) After loading the TsFile file，reported an error In a clean server
[ https://issues.apache.org/jira/browse/IOTDB-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reopened IOTDB-1330: --- > After loading the TsFile file，reported an error In a clean server > -- > > Key: IOTDB-1330 > URL: https://issues.apache.org/jira/browse/IOTDB-1330 > Project: Apache IoTDB > Issue Type: Bug > Components: Server >Affects Versions: 0.12.0 >Reporter: xiaozhihong >Assignee: Houliang Qi >Priority: Major > Labels: pull-request-available > > step 1： > No partition,write data by benchmark, and enter cli, then query data, > finally flush. > step 2: > Backup the generated TsFile file to new route > step 3: > Start a clean server, open the partition > step4: > Enter cli, load the TsFile > Actually，load failed > load "/home/xzh/0.12.0/load_TsFile/1619502355580-1-0-0.tsfile" true > Msg: 411: Cannot load file > /home/xzh/0.12.0/load_TsFile/1619502355580-1-0-0.tsfile because null > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1345) AlertManagerTest: Bind Address already in use
Steve Yurong Su created IOTDB-1345: -- Summary: AlertManagerTest: Bind Address already in use Key: IOTDB-1345 URL: https://issues.apache.org/jira/browse/IOTDB-1345 Project: Apache IoTDB Issue Type: Test Components: Core/Engine Reporter: Steve Yurong Su Attachments: image-2021-04-29-15-53-50-971.png !image-2021-04-29-15-53-50-971.png! [https://github.com/apache/iotdb/pull/3105/checks?check_run_id=2464481508] https://github.com/apache/iotdb/pull/3104/checks?check_run_id=2464458468 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1331) AVG not work in cluster mode.
[
https://issues.apache.org/jira/browse/IOTDB-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335196#comment-17335196
]
sunjincheng commented on IOTDB-1331:
Thanks for the useful feedback. [~jt2594838]
I think if we can know the type of path (PartialPath or VectorPartialPath) in
advance, we can decide whether to call the `transformPaths` method according to
the type of paths, thereby reducing the access to remote Meta Call.
Unfortunately, we have no way to know the type of path without Meta info(make
sense).
we can get less binefit if we add implemention fo access remote Meta in
MManager. The responsibility of accessing remote Meta should be CMManager. But
for the transformPath method, both CMManager and MManager should have it. So I
suggest to add transformPath to CMManager and check PR[1] in detail. Any
feedback is welcome.
[1] https://github.com/apache/iotdb/pull/3105
> AVG not work in cluster mode.
> -
>
> Key: IOTDB-1331
> URL: https://issues.apache.org/jira/browse/IOTDB-1331
> Project: Apache IoTDB
> Issue Type: Sub-task
> Components: Cluster
>Reporter: sunjincheng
>Assignee: sunjincheng
>Priority: Major
> Fix For: 0.12.1, 0.13.0
>
>
> The AVG not work after the commit :
> https://github.com/apache/iotdb/commit/aaa8fecf8526df316c06fe3b1bf2954ef1dbdfb8
>
> {code}
> IoTDB> select avg(temperature) from root.ln.wf01.wt01;
> Msg: 411: Error occurred in query process: Path
> [root.ln.wf01.wt01.temperature] does not exist
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1344) Deleting Storage Group does not clear the count of time series
Jialin Qiao created IOTDB-1344: -- Summary: Deleting Storage Group does not clear the count of time series Key: IOTDB-1344 URL: https://issues.apache.org/jira/browse/IOTDB-1344 Project: Apache IoTDB Issue Type: Bug Components: Schema Manager Affects Versions: 0.11.3, 0.12.0, master branch Reporter: Jialin Qiao Set parameter in iotdb-env.sh MAX_HEAP_SIZE="1G" HEAP_NEWSIZE="1G" Set parameter in iotdb-engine.properties estimated_series_size=5 Then, execute: create timeseries root.turbine1.1701.s1 with datatype=FLOAT, encoding=RLE, compression=SNAPPY delete storage group root.turbine1 create timeseries root.turbine1.1701.s2 with datatype=FLOAT, encoding=RLE, compression=SNAPPY You get: Msg: 303: IoTDB system load is too large to create timeseries, please increase MAX_HEAP_SIZE in iotdb-env.sh/bat and restart -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1343) Can not start server when only set MAX_HEAP_SIZE to a small number
Jialin Qiao created IOTDB-1343: -- Summary: Can not start server when only set MAX_HEAP_SIZE to a small number Key: IOTDB-1343 URL: https://issues.apache.org/jira/browse/IOTDB-1343 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.12.0 Reporter: Jialin Qiao Attachments: image-2021-04-29-15-04-45-528.png In a machine with 16G memory, set MAX_HEAP_SIZE="1G" in iotdb-env.sh Then, start-server.sh !image-2021-04-29-15-04-45-528.png! It's better to auto adjust the HEAP_NEWSIZE if it is larger than MAX_HEAP_SIZE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1342) Verify that LIMIT and OFFSET are used in conjunction with the FILL clause, and the error message is inconsistent with the system service
xiaozhihong created IOTDB-1342: -- Summary: Verify that LIMIT and OFFSET are used in conjunction with the FILL clause, and the error message is inconsistent with the system service Key: IOTDB-1342 URL: https://issues.apache.org/jira/browse/IOTDB-1342 Project: Apache IoTDB Issue Type: Bug Components: Document Affects Versions: 0.12.0 Reporter: xiaozhihong Attachments: image-2021-04-29-15-03-40-134.png !image-2021-04-29-15-03-40-134.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1239) Incorrect datetime value can be inserted into iotdb successfully.
[
https://issues.apache.org/jira/browse/IOTDB-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335184#comment-17335184
]
刘珍 commented on IOTDB-1239:
---
这个报错也有问题，和insert成功的表现不一致。
!image-2021-04-29-14-54-43-270.png!
> Incorrect datetime value can be inserted into iotdb successfully.
> -
>
> Key: IOTDB-1239
> URL: https://issues.apache.org/jira/browse/IOTDB-1239
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/CLI
>Reporter: 刘珍
>Priority: Minor
> Labels: pull-request-available
> Attachments: image-2021-04-29-14-54-43-270.png
>
>
> master branch.
> commit id 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7 .
>
> SET STORAGE GROUP TO root.sg
> CREATE TIMESERIES root.sg.d1.s2 WITH DATATYPE=DOUBLE, ENCODING=PLAIN
> insert into root.sg.d1(time,s2 ) values (15741792,8.76);
> IoTDB> select * from root.sg.d1;
> +---+-+
> | Time|root.sg.d1.s2|
> +---+-+
> |{color:#FF}+{color}51853-10-03T00:00:{color:#FF}.0{color}+08:00|
> 8.76|
> +---+-+
> {color:#FF}should be give an error :{color}
> {color:#FF}Incorrect datetime value {color}
> IoTDB> select * from root.sg.d1 where time=51853-10-03T00:00:.0+08:00
> Msg: 401: Error occurred while parsing SQL to physical plan: line 1:36
> extraneous input '51853-10-03T00:00:' expecting \{NOW, TRUE, FALSE, '-', '.',
> 'NaN', INT, EXPONENT, DATETIME, DOUBLE_QUOTE_STRING_LITERAL,
> SINGLE_QUOTE_STRING_LITERAL}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
