[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] [Assigned] (IOTDB-1641) CMManager support Vector
[ https://issues.apache.org/jira/browse/IOTDB-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hai Liu reassigned IOTDB-1641: -- Assignee: Zesong Sun (was: Quan Siyi) > CMManager support Vector > > > Key: IOTDB-1641 > URL: https://issues.apache.org/jira/browse/IOTDB-1641 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Hai Liu >Assignee: Zesong Sun >Priority: Major > Original Estimate: 120h > Remaining Estimate: 120h > -- 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] [Created] (IOTDB-1748) Comb cluster query process
Xinyu Tan created IOTDB-1748: Summary: Comb cluster query process Key: IOTDB-1748 URL: https://issues.apache.org/jira/browse/IOTDB-1748 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Xinyu Tan Assignee: Xinyu Tan The current cluster read process is encapsulated in the seriesReader layer so that data can be fetched remotely. In fact, it's easy to understand the cluster query process once you understand the standalone query process. However, this also requires a detailed documentation for an introduction. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1747) Support for automatically creating schemas for aligned time series in cluster module
Xinyu Tan created IOTDB-1747: Summary: Support for automatically creating schemas for aligned time series in cluster module Key: IOTDB-1747 URL: https://issues.apache.org/jira/browse/IOTDB-1747 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Xinyu Tan Assignee: Xinyu Tan Automatic schema creation for aligned time series needs to be supported to ensure that users can write properly -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1746) DataGroup snapshots support align timeseries
Xinyu Tan created IOTDB-1746: Summary: DataGroup snapshots support align timeseries Key: IOTDB-1746 URL: https://issues.apache.org/jira/browse/IOTDB-1746 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan Snapshots of the meta group in the current cluster module support normal timeseries, but do not support align timeseries. Alignd timeseries need to be supported so that if the user uses aligned time series, there will be no error when catchup is started between nodes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1745) Metagroup snapshots support template
Xinyu Tan created IOTDB-1745: Summary: Metagroup snapshots support template Key: IOTDB-1745 URL: https://issues.apache.org/jira/browse/IOTDB-1745 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Xinyu Tan Assignee: Xinyu Tan Snapshots of the meta group in the current cluster module support storage groups and TTL information, etc, but do not support templates. Templates need to be supported so that newly added nodes can register templates during cluster expansion. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1744) Support more aggregation functions in the group by fill
Minghui Liu created IOTDB-1744: -- Summary: Support more aggregation functions in the group by fill Key: IOTDB-1744 URL: https://issues.apache.org/jira/browse/IOTDB-1744 Project: Apache IoTDB Issue Type: New Feature Reporter: Minghui Liu Assignee: Minghui Liu Fix For: master branch, 0.12.3 Now, only last_value aggregation function is supported in group by fill. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1726) Wrong hashCode() and equals() method in ChunkMetadata
[
https://issues.apache.org/jira/browse/IOTDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minghui Liu reassigned IOTDB-1726:
--
Assignee: Minghui Liu
> Wrong hashCode() and equals() method in ChunkMetadata
> -
>
> Key: IOTDB-1726
> URL: https://issues.apache.org/jira/browse/IOTDB-1726
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Engine
>Affects Versions: 0.12.2
>Reporter: Yuan Tian
>Assignee: Minghui Liu
>Priority: Major
>
> {code:java}
> @Override
> public boolean equals(Object o) {
> if (this == o) {
> return true;
> }
> if (o == null || getClass() != o.getClass()) {
> return false;
> }
> ChunkMetadata that = (ChunkMetadata) o;
> return offsetOfChunkHeader == that.offsetOfChunkHeader
> && version == that.version
> && Objects.equals(measurementUid, that.measurementUid)
> && tsDataType == that.tsDataType
> && Objects.equals(deleteIntervalList, that.deleteIntervalList)
> && Objects.equals(statistics, that.statistics);
> }
> @Override
> public int hashCode() {
> return Objects.hash(
> measurementUid, deleteIntervalList, tsDataType, statistics, version,
> offsetOfChunkHeader);
> }
> {code}
> We can see that chunkmetadata use version to differentiate, however, in
> different storage groups, different file's version may be same. That means
> root.sg1.d1.s1 and root.sg2.d1.s1 may share the same cache entry in ChunkCache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IOTDB-1280) Rewrite the Antlr grammar file
[ https://issues.apache.org/jira/browse/IOTDB-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minghui Liu reassigned IOTDB-1280: -- Assignee: Minghui Liu > Rewrite the Antlr grammar file > -- > > Key: IOTDB-1280 > URL: https://issues.apache.org/jira/browse/IOTDB-1280 > Project: Apache IoTDB > Issue Type: Task > Components: Planner/SQLParser >Reporter: Xiangdong Huang >Assignee: Minghui Liu >Priority: Major > > Current antlr g4 file is not elegant. > 1. We should realize that Lexer and Parser having different usage: > - Lexer is for considering something into one "word", i.e., a string that > will not be split in users' program. E.g., "abcdere324234", "-2.0", "-2e5", > "root.sg.a.b" (if we do not split the path any more... which is impossible). > All rules that belong to Lexer should start with a Capital Char. > - Parser is for generating AST. According to Antlr's introduction articles, > parser is more time consuming than lexer. The fewer rules that parser has, > the faster. > That is, if something can be defined in Lexer, we should not define them as > parser. > IMO, the principle is: > - if we need to split a word into several words, then put the rule into > parser; E.g., "1h"/"1m", as we have to split the word and get its time unit, > why not define it as two words directly in Antlr (i.e., do not define a > lexer rule like: "DURATION: (INT+ (Y|M O|W|D|H|M|S|M S|U S|N S))+")? > More, we can test whether a lexer is fast enough for checking a Path. If so, > we do not define another Pattern in our program to check whether a time > series name is legal. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [iotdb-bin-resources] SteveYurongSu merged pull request #5: Doc:add IoTDB-InfluxDB image
SteveYurongSu merged pull request #5: URL: https://github.com/apache/iotdb-bin-resources/pull/5 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-bin-resources] jun0315 opened a new pull request #5: Doc:add IotDB-InfluxDB image
jun0315 opened a new pull request #5: URL: https://github.com/apache/iotdb-bin-resources/pull/5 Doc:add IotDB-InfluxDB image -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (IOTDB-1701) The naming rules of the tested database need to be unified (all uppercase is recommended)
[ https://issues.apache.org/jira/browse/IOTDB-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 张洪胤 reassigned IOTDB-1701: -- Assignee: 张洪胤 > The naming rules of the tested database need to be unified (all uppercase is > recommended) > - > > Key: IOTDB-1701 > URL: https://issues.apache.org/jira/browse/IOTDB-1701 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Assignee: 张洪胤 >Priority: Minor > > The current part of the database name has both uppercase and lowercase > letters, which is too cumbersome. > Such as,DB_SWITCH=IoTDB-012-SESSION_BY_TABLET；DB_SWITCH=InfluxDB -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1743) Add array and list data type
Jialin Qiao created IOTDB-1743: -- Summary: Add array and list data type Key: IOTDB-1743 URL: https://issues.apache.org/jira/browse/IOTDB-1743 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Support array and list data type. the array has fixed length while list not -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1699) Verification of the way of recording data set, optimization items needed to generate data set
[ https://issues.apache.org/jira/browse/IOTDB-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420242#comment-17420242 ] xiaozhihong commented on IOTDB-1699: [https://github.com/thulab/iotdb-benchmark/pull/193https://github.com/thulab/iotdb-benchmark/pull/193|https://github.com/thulab/iotdb-benchmark/pull/193] > Verification of the way of recording data set, optimization items needed to > generate data set > - > > Key: IOTDB-1699 > URL: https://issues.apache.org/jira/browse/IOTDB-1699 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Priority: Critical > > Issue1: > Whether the TEXT file is limited in size (involving the testable data size) > (currently not limited, need to investigate) > note: > I met an error when the TXT file generated by writing the data set was larger > than 500M, and then I didn’t know where to fix it and there was no error > currently. We need to check to write and query after the data set generation > mode> 500M. > Issue2: > Optimize one TEXT file can put multiple batches (currently one batch writes > one file) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1672) Separate AlignedInsertPlan from current InsertPlan
[ https://issues.apache.org/jira/browse/IOTDB-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yukun Zhou reassigned IOTDB-1672: - Assignee: Yukun Zhou > Separate AlignedInsertPlan from current InsertPlan > -- > > Key: IOTDB-1672 > URL: https://issues.apache.org/jira/browse/IOTDB-1672 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Query, Core/Schema Manager, Core/Server >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Fix For: 0.13.0 > > Attachments: image-2021-09-13-10-42-24-943.png > > > IoTDB support timeseries and aligned timeseries, in other words, unary > measurement and vector measurement. > Currently, the insert plans of these two types of timeseries is distinguished > by a "boolean isAligned" field and share the same interface and code. Thus > the related code will be confusing and difficult to understand. > For example. While MManager is processing the InsertPlan, the path and > measurement list provided by the plan represent different meaning. > # While process unary measurement, the prefix path means the entity path and > the measurement list represents different measurement of target timeseries. > # While process vector measurement, the prefix path represents the aligned > timeseries path and the measurement list represents the sub measurement of > target aligned timeseries. > !image-2021-09-13-10-42-24-943.png|width=534,height=294! > > Thus, it's better to process aligned timeseries insert plan individually and > the code will be more understandable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1742) IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2
[ https://issues.apache.org/jira/browse/IOTDB-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420238#comment-17420238 ] Jialin Qiao commented on IOTDB-1742: !image-2021-09-26-17-22-08-156.png! !image-2021-09-26-17-21-55-669.png! > IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2 > - > > Key: IOTDB-1742 > URL: https://issues.apache.org/jira/browse/IOTDB-1742 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Steve Yurong Su >Assignee: Steve Yurong Su >Priority: Major > Attachments: image-2021-09-26-17-04-26-042.png, > image-2021-09-26-17-21-55-669.png, image-2021-09-26-17-22-08-156.png > > > !image-2021-09-26-17-04-26-042.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1700) Unification of HOST: For the current host, some need to add http format, and some need to add ip directly.
[ https://issues.apache.org/jira/browse/IOTDB-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420237#comment-17420237 ] xiaozhihong commented on IOTDB-1700: https://github.com/thulab/iotdb-benchmark/pull/193 > Unification of HOST: For the current host, some need to add http format, and > some need to add ip directly. > -- > > Key: IOTDB-1700 > URL: https://issues.apache.org/jira/browse/IOTDB-1700 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Priority: Minor > > For example: > IoTDB's HOST=localhost, like InfluxDB's host is HOST=http://localhost -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1701) The naming rules of the tested database need to be unified (all uppercase is recommended)
[ https://issues.apache.org/jira/browse/IOTDB-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420236#comment-17420236 ] xiaozhihong commented on IOTDB-1701: https://github.com/thulab/iotdb-benchmark/pull/193 > The naming rules of the tested database need to be unified (all uppercase is > recommended) > - > > Key: IOTDB-1701 > URL: https://issues.apache.org/jira/browse/IOTDB-1701 > Project: Apache IoTDB > Issue Type: Improvement > Components: Benchmark >Reporter: xiaozhihong >Priority: Minor > > The current part of the database name has both uppercase and lowercase > letters, which is too cumbersome. > Such as,DB_SWITCH=IoTDB-012-SESSION_BY_TABLET；DB_SWITCH=InfluxDB -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1675) Introduce UnaryMeasurementMNode and VectorMeasurementMNode
[ https://issues.apache.org/jira/browse/IOTDB-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yukun Zhou reassigned IOTDB-1675: - Assignee: Yukun Zhou > Introduce UnaryMeasurementMNode and VectorMeasurementMNode > -- > > Key: IOTDB-1675 > URL: https://issues.apache.org/jira/browse/IOTDB-1675 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Schema Manager, Core/Server >Reporter: Yukun Zhou >Assignee: Yukun Zhou >Priority: Major > Fix For: 0.13.0 > > Attachments: image-2021-09-13-11-29-04-803.png > > > Currently, unary measurement schema and vector measurement schema is hold by > MeasurementMNode. The unary case and vector case is distinguished by schema > type check. > To make the code more clean, it's better to separate the process of two > cases into different methods and set specialized param, like > UnaryMeasurementMNode and VectorMeasurementMNode, to avoid redundant schema > check. And the separation will make the code more explicit and easy to > maintain. > Besides, some features like alias, tag, and trigger do not support vector > case for the time being. These should be separated from the unary case for > future implementation and extension. > > !image-2021-09-13-11-29-04-803.png|width=477,height=299! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1742) IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2
Steve Yurong Su created IOTDB-1742: -- Summary: IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2 Key: IOTDB-1742 URL: https://issues.apache.org/jira/browse/IOTDB-1742 Project: Apache IoTDB Issue Type: Bug Reporter: Steve Yurong Su Attachments: image-2021-09-26-17-04-26-042.png !image-2021-09-26-17-04-26-042.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1742) IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2
[ https://issues.apache.org/jira/browse/IOTDB-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Yurong Su reassigned IOTDB-1742: -- Assignee: Steve Yurong Su > IT fails on IoTDBContinuousQueryIT.testContinuousQueryResult2 > - > > Key: IOTDB-1742 > URL: https://issues.apache.org/jira/browse/IOTDB-1742 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Steve Yurong Su >Assignee: Steve Yurong Su >Priority: Major > Attachments: image-2021-09-26-17-04-26-042.png > > > !image-2021-09-26-17-04-26-042.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1571) Vector data query fail after IoTDB restart
[ https://issues.apache.org/jira/browse/IOTDB-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420223#comment-17420223 ] Haonan Hou commented on IOTDB-1571: --- https://github.com/apache/iotdb/pull/3917 > Vector data query fail after IoTDB restart > -- > > Key: IOTDB-1571 > URL: https://issues.apache.org/jira/browse/IOTDB-1571 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Server >Reporter: Yukun Zhou >Assignee: Haonan Hou >Priority: Major > Labels: pull-request-available > Fix For: master branch > > > Case: > # Start IoTDB > # Start Session to create aligned timeseries and insert data > # Use CLI to query data, (e.g. select * from root.sg.d.vector.s) and the > resultDataSet contains all wanted data > # Restart IoTDB > # Use CLI to query data again and the resultDataSet is Empty > This problem is a stable repetition. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1741) Compaction file stream clsoed Exception
Liuxuxin created IOTDB-1741: --- Summary: Compaction file stream clsoed Exception Key: IOTDB-1741 URL: https://issues.apache.org/jira/browse/IOTDB-1741 Project: Apache IoTDB Issue Type: Bug Reporter: Liuxuxin Assignee: Liuxuxin Fix For: 0.12.2 Attachments: image-2021-09-26-15-30-39-569.png !image-2021-09-26-15-30-39-569.png! Compaction IOException in 0.12.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1726) Wrong hashCode() and equals() method in ChunkMetadata
[
https://issues.apache.org/jira/browse/IOTDB-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420219#comment-17420219
]
Jialin Qiao commented on IOTDB-1726:
(1) use fileVersion and chunkOffset in equals and hashCode methods
(2) Let all tsfiles in an instance to share one SimpleFileVersionController,
not each partition+sg
> Wrong hashCode() and equals() method in ChunkMetadata
> -
>
> Key: IOTDB-1726
> URL: https://issues.apache.org/jira/browse/IOTDB-1726
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Engine
>Reporter: Yuan Tian
>Priority: Major
>
> {code:java}
> @Override
> public boolean equals(Object o) {
> if (this == o) {
> return true;
> }
> if (o == null || getClass() != o.getClass()) {
> return false;
> }
> ChunkMetadata that = (ChunkMetadata) o;
> return offsetOfChunkHeader == that.offsetOfChunkHeader
> && version == that.version
> && Objects.equals(measurementUid, that.measurementUid)
> && tsDataType == that.tsDataType
> && Objects.equals(deleteIntervalList, that.deleteIntervalList)
> && Objects.equals(statistics, that.statistics);
> }
> @Override
> public int hashCode() {
> return Objects.hash(
> measurementUid, deleteIntervalList, tsDataType, statistics, version,
> offsetOfChunkHeader);
> }
> {code}
> We can see that chunkmetadata use version to differentiate, however, in
> different storage groups, different file's version may be same. That means
> root.sg1.d1.s1 and root.sg2.d1.s1 may share the same cache entry in ChunkCache
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
